topic Re: Activiti causes Exception 'Transaction is not active in the current thread' in Alfresco Archive

Activiti causes Exception 'Transaction is not active in the current thread'

stephan_bauer — Wed, 11 Mar 2015 18:10:49 GMT

Dear Activiti-Team,we have a setup with Activiti (5.16.3) inside Glassfish from which it should get its transactions, because of the following transactionManager-configuration in activiti-standalone-context.xml: <jee:jndi-lookup jndi-name="java:appserver/TransactionManager" id="transactionManag

Re: Activiti causes Exception 'Transaction is not active in the current thread'

jbarrez — Tue, 17 Mar 2015 09:10:17 GMT

Hmmm in the logs you posted : "org.activiti.engine.impl.interceptor.JtaTransactionInterceptor:45 - Running command with propagation REQUIRED"

If I'm correct, this should start a new transaction in JTA, right? So i'm a bit puzzled.

I'm assuming it used to work before? What config where you using then?

Re: Activiti causes Exception 'Transaction is not active in the current thread'

stephan_bauer — Fri, 20 Mar 2015 14:44:10 GMT

Hi Joram,

finally the problem has gone away. Our main problem was, that our servicetasks were not threadsafe. I wasn't aware that they have to. Thus we had some instance variables like the processinstanceid. This led of course to chaotic behavior when a second or even more threads were using the same instance of a servicetask. In the course of analyzing the problems we had several other exception types as well. We finally decided to migrate to Jboss Wildfly 8.2, even though we now can strongly assume, that Glassfish was not to blame.

Nevertheless many thanks,
Stephan

Re: Activiti causes Exception 'Transaction is not active in the current thread'

jbarrez — Tue, 24 Mar 2015 13:31:19 GMT

Allright thanks for posting back. Yes, indeed delegates should be thread safe.
But I'm still not sure how that relates to the JTA problem though … any more insight into why, from a technical view, that happened?