XA Datasource: ERROR [ims.jdbc.connections] (Thread-30 (HornetQ-client-global-threads-606925674)) Connection commit failed java.sql.SQLException: You cannot commit during a managed transaction!

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

I'm working on standing up a new IDM environment for an upgrade (standalone installation not vApp).  In the upgraded Dev environment, we have enabled XA datasources for the IDM default datasources.  In the new QA environment, I'm getting errors complaining about autocommit being on and not supported in XA.  Here's a snippet of the error.

16:55:44,129 ERROR [ims.jdbc.connections] (Thread-30 (HornetQ-client-global-threads-606925674)) Connection commit failed with exception:You cannot commit during a managed transaction!: java.sql.SQLException: You cannot commit during a managed transaction!
 at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.jdbcCommit(BaseWrapperManagedConnection.java:1070)
 at org.jboss.jca.adapters.jdbc.WrappedConnection.commit(WrappedConnection.java:759)
 at com.netegrity.idmutils.DBConnectionUtil.closeConnection(DBConnectionUtil.java:70) [idmutils.jar:]
 at com.netegrity.ims.util.TaskSessionSequence.updateEnvironment(TaskSessionSequence.java:176) [ims.jar:]

The strange part is if I am in the management console of node1 and save something and restart the environment, the error shows up on node 2, and vice-versa, if I do the change in the management console on node 2 and restart the environment, the error shows on node 1.

I have restarted JBoss on both servers, but the error continues. 

Environment

Release : 14.3 (GA --no CPs applied)

Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)

Resolution

The errors were resolved after applying CP2 to the GA version of 14.3.

Apply CP2 or highest available Cumulative patch.