The application in question contains a Stateful Session Bean (SFSB) which has one method which runs for a particularly long time. In my case some times for several minutes. However after exactly 10 minutes the transaction is rollback and an exception is thrown to the client. I already tried increasing the max-bean-age and max-bean-life for the "Standard Stateful SessionBean" and "Clustered Stateful SessionBean" in conf/standardjboss.xml as well as increased the TransactionTimeout from 300 to 450 in conf/standardjboss.xml.
After exaction 450 seconds since invoking the long running method the following log messages are reported :
20:18:27,543 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fd2d:e48e:4cf8de0f:bc invoked while multiple threads active within it.
20:18:27,544 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fd2d:e48e:4cf8de0f:bc aborting with 1 threads active!
And after 600 seconds
20:20:57,708 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action -3f57fd2d:e48e:4cf8de0f:bc\
and the following exception is thrown to the client
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
My question is where do I set the default transaction time which seems to be set to 600 seconds. I know there is an option in jboss.xml as well as an annotation. However I am looking for the place where the default global setting can be changed.