Atomikos Forum

I was using atomikos transaction manager along with spring transaction when using jboss cache(infinispan).

One of their usecases was not working and i have raised a jira bug.

They say teh behaviour is because teh cache put and transaction commit happens in a different thread.

https://issues.jboss.org/browse/ISPN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

The logs show that the thread name as Atomikos 1

2011-02-15 10:23:08,024 25143 TRACE [org.infinispan.interceptors.DistributionInterceptor] (Atomikos:1:) Affected keys in context LocalTxInvocationContext{flags=null}@9866417 are: []
2011-02-15 10:23:08,024 25143 TRACE [org.infinispan.distribution.DistributionManagerImpl] (Atomikos:1:) Affected keys are empty


So my question is does JTA allow the transaction commit to happen in a seperate thread (other thread than invoked by
teh user) ?

This is because you did not disable threaded commit. Just try this:

-in jta.properties, set com.atomikos.icatch.threaded_2pc=false

HTH

Thanks . it seems to work fine when i set this to false.

Is this particular optimization specific to atomikos or is it guided by JTA specs ?

This is Atomikos-specific.

HTH