topic Transaction warning in JBoss in Alfresco Archive

Transaction warning in JBoss

drams — Tue, 05 Nov 2013 13:31:00 GMT

We are preparing to go in to production for a important public-facing platform and we are doing some last cleans up checks. While doing this we are noticing that there are some warnings being logged by/during Activiti actions in our log files, which we would like to investigate. All functionalitity

Re: Transaction warning in JBoss

frederikherema1 — Thu, 07 Nov 2013 10:41:30 GMT

Yes, indeed. That warning won't be shown anymore (see https://github.com/Activiti/Activiti/commit/454d51765ba6a8cbd3806eae4f371ac4c6b003f5).

I'm affraid I can't help you with the second warning, never came across this issue. Any chance on revealing the name of this important public-facing project?

Re: Transaction warning in JBoss

jolacitrouille — Mon, 12 May 2014 16:04:30 GMT

Hi, I am using activiti 5.15.1 on a JBoss EAP 5.1.2 in combination with an Oracle database using a XA datasource and guess what.. I am having the exact same problem 🙂

<code>
18:01:53,552 WARN [UserTransactionRegistry] Error notifying listener org.jboss.resource.connectionmanager.CachedConnectionManager@3d24d8 of userTransactionStarted
java.lang.IllegalStateException: Trying to change transaction TransactionImple < ac, BasicAction: a0a7047:cb8c:5370f051:212 status: ActionStatus.RUNNING > in enlist!
</code>

Did you figure the problem out ?

Thanks for your help!

Re: Transaction warning in JBoss

jolacitrouille — Fri, 16 May 2014 14:07:18 GMT

Ok, after some investigations, I realized a command was executed in a transaction with the config REQUIRES_NEW… This happens in DbIdGenerator#getNewBlock… Climbing it up, I realized that idGenerator in ProcessEngineConfigurationImpl was init with <code>dbIdGenerator.setCommandConfig(getDefaultCommandConfig().transactionRequiresNew())</code>… (in ProcessEngineConfigurationImpl#initIdGenerator)
Why is it defaulted to REQUIRES_NEW ?
JBoss doesn't seem to like it very much…

Re: Transaction warning in JBoss

nagyf — Fri, 23 May 2014 14:12:19 GMT

Hi!

I'm using the latest Activiti (5.15.1) release with JBoss 6.1 EAP, and experiencing the same problem, we get the same exception.
Activiti configured to use the transaction manager of JBoss, obtained via JNDI, the datasource also configured in JBoss.

Do you have any updates on it?
Is it safe to ignore this warning?
Anybody know how to fix this?

Thank you for any help!

Re: Transaction warning in JBoss

jbarrez — Tue, 27 May 2014 08:23:28 GMT

If the comment above is correct about REQUIRES_NEW, it might be good to try the UUID id generator: http://activiti.org/userguide/index.html#advanced.uuid.generator

This way, the default db id generator shouldn't need to start a transaction with REQUIRES_NEW

Re: Transaction warning in JBoss

nagyf — Tue, 27 May 2014 08:34:40 GMT

I've just tested it, and it works.

Thanks for your help!

Re: Transaction warning in JBoss

jbarrez — Fri, 30 May 2014 08:30:52 GMT

Awesome. Thanks for posting back!