Error message "Illegal TXN State: Attempt to start new transaction during rollback" in RSA Identity Governance & Lifecycle
Originally Published: 2017-12-04
Last Modified: 2023-09-25
Article Number
000040597
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1 +
Application Server: Jboss
Issue
The RSA Identity Governance & Lifecycle user interface is inaccessible with an initialization error "Illegal TXN State: Attempt to start new transaction during rollback. Txm count=1".

User-added image
Cause
Looking into the server.log and aveksaServer.log, it seems that there is a huge backlog of JMX transactions and the JBOSS server is attempting to replay the transactions during RSA Identity Governance & Lifecycle startup.
  
2017-12-01 01:49:41,635 WARN [com.workpoint.client.ClientContext] Attempt failed to retrieve authorization options from server. Either the server is not running or the client configuration may not be set up correctly. See the client log file for details.
2017-12-01 01:49:41,634 WARN [com.workpoint.client.ClientContext] Attempt failed to retrieve authorization options from server. Either the server is not running or the client configuration may not be set up correctly. See the client log file for details.
2017-12-01 01:49:41,635 INFO [STDOUT] 2017-12-01 01:49:41,635 [Timer-8] ERROR com.workpoint.queue.core.QMonitor - Attempt failed to create a client context. The monitors will not execute properly without this connection to the server.
java.rmi.RemoteException: Attempt failed to retrieve authorization options from server. Either the server is not running or the client configuration may not be set up correctly. See the client log file for details.
at com.workpoint.client.ClientContext.retrieveAuthInfo(Unknown Source)
at com.workpoint.client.ClientContext.open(Unknown Source)
at com.workpoint.client.ClientContext.open(Unknown Source)
at com.workpoint.queue.core.QMonitor.F(Unknown Source)
at com.workpoint.queue.core.QMonitor.I(Unknown Source)
at com.workpoint.queue.core.QMonitor.startMonitor(Unknown Source)
at com.workpoint.queue.WpQMonitors$_A.run(Unknown Source)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Resolution
Clear the backlog or stuck JMX transactions using the steps below.
  1. Stop the RSA Identity Governance & Lifecycle services. 
    service aveksa_server stop
  2. Delete or rename the /home/oracle/jboss-4.2.2.GA/server/default/data/tx-object-store directory.
  3. Start the RSA Identity Governance & Lifecycle services. 
    service aveksa_server start
   

Related Articles

Trending Articles

Don't see what you're looking for?