Atomikos Forum

Can someone explain to me what might be causing these messages?

09-06 09:05:50 WARN  [Atomikos:14] (ActiveStateHandler:12) - Timeout/setRollbackOnly of ACTIVE coordinator !

At times I am seeing a ton of these messages.  I can go hours without any - while during other times get over 3900 per minute.

It seems like it would be some type of environmental issue between the app server and the db server - but I am having a heck of a time figuring it out.

More context...

I have this same application running in 2 different places - One that has this problem - and the other which does not.  This is why I think it must be something outside the code itself.

Also, I am getting 2 other errors on the one server but not the other --- not sure if they are all related.

----------------------------------------------------
org.springframework.transaction.UnexpectedRollbackException: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is javax.transaction.RollbackException: Prepare: NO vote
    at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1012)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
    at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)

----------------------------------------------------
java.sql.SQLRecoverableException: IO Error: Connection timed out

There are timeouts - probably connection issues in the DB.

You could try setting a testquery on the datasource and increasing  transaction timeout parameter...