Following on from my previous topic (default82df.html?community.6.1524.0) I think I may have found a bug in Atomikos. If I kill the transaction manager during commit of a transaction involving a JMS and database resource, at the point in the Atomikos source code immediately after the line 'coordinator_.setState ( TxState.COMMITTING );' in the CoordinatorStateHandler.commit(boolean, boolean) method, and then restart the transaction manager, my log gets spammed with the following message:
Exception on timeout of coordinator 188.8.131.52.tm0004700003: null
The is caused by a null pointer exception in the class HeurHazardStateHandler.onTimeout() method: 'boolean committed = getCommitted ().booleanValue ();'
The _committed value is null, hence the null pointer exception.
If I move the line of code 'committed_ = new Boolean ( true );' in the CoordinatorStateHandler.commit(boolean, boolean) method to before the 'coordinator_.setState ( TxState.COMMITTING );' line, then everything seems to work ok, there is no NullPointerException.
Is this an atomikos bug? If not any indications what might be wrong with my configuration?
This topic is archived. No further replies will be accepted.Other recent topics