RSA Via Lifecycle and Governance Workflow fails with error "Illegal TXN State: Attempt to start new transaction during rollback"
4 years ago
Originally Published: 2016-02-04
Article Number
000063099
Applies To
RSA Product Set:  RSA Via Lifecycle and Governance
RSA Version/Condition:  6.9.1
Platform:  WebLogic or WebSphere
 
Issue
Workflow errors occur on WebLogic or WebSphere servers configured as a cluster.  Workflows may fail.  The "Illegal TXN State" errors are usually associated with other workflow errors and the type of error may vary. 

The following error is logged in the ../aveksa.ear/aveksa.war/log/aveksaServer.log: 
09/24/2015 19:49:56.061 ERROR ([ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)') [com.aveksa.UI] 
com.aveksa.gui.core.filters.WorkflowContextFilter.addWorkflowContextInformation(WorkflowContextFilter.java:188) - 
java.lang.RuntimeException: Illegal TXN State: Attempt to start new transaction during rollback. Txn count=1

The following error is logged in the ../aveksa.ear/aveksa.war/log/WorkPoint.log: 
2015-08-06 21:51:03,675 [Worker_actionq#ActionQ1#WPDS_337] ERROR com.workpoint.server.pojo.GenericServerBean - RecordSetException occurred: Concurrency error. 
Another user has updated this Job object since you selected it. Please re-select Job 6115:WPDS and attempt this operation again.
Cause
This error indicates a problem managing the rollback of failed transactions due to other workflow failures.  If a Workflow generates an exception during execution that causes the workflow to fail the workflow manager will attempt to roll back any transactions started in that Workflow.  While a transaction rollback is happening, other Workflows may be blocked until the rollback is complete.  If a large number of workflows are failing at the same time the backlog of transactions waiting for rollback may cause other workflows to fail with the message "Illegal TXN State."

This issue may occur on all server types, but is more common on WebLogic and WebSphere servers deployed as a cluster as the transaction rollback on these systems leverages JMS messaging for control which limits the practical throughput.

Resolution
The way Workflow transactions are committed to the database has been changed in 6.9.1 P11 in order to reduce the chance database collisions during transaction rollback. If your system displays this error apply 6.9.1 patch P11 or later. 
 
Workaround
The problem with record locking during transaction rollback only occurs when transaction are being rolled back due to other Workflow errors.  

Identify and correct any other workflow errors that are occurring on the system even if these errors are not directly of concern.  Transaction rollback is inherently expensive and should be avoided if at all possible. 

Related Articles

Trending Articles

Don't see what you're looking for?