JTA Timeout Errors - BPEL 10g

JTA Timeout Errors - BPEL 10g

As a BPEL Developer, you may have come across many times the below error -

"JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1255921-BpInv2-BpSeq2.5-5......"

Basically, you will get this JTA timeout error if some of the partner links in your BPEL are taking so much of time than the default specified transaction time value on the OC4J app server for BPEL execution. Then, you need follow the below steps to tune your BPEL engine to take care of the transaction processing.

Set the transaction-timeout and syncMaxWaitTime properties as follows:

Property	File Location	This Value Must Be...	Example
transaction-timeout	SOA_Oracle_Home\j2ee\home\config\transaction-manager.xml	Larger than the transaction-timeout value in orion-ejb-jar.xml and the syncMaxWaitTime value.	7200
transaction-timeout	SOA_Oracle_Home\j2ee\home\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml	Less than the transaction-timeout value in transaction-manager.xml. Note: You must set all transaction-timeout properties that display in this file.	3600
syncMaxWaitTime	SOA_Oracle_Home\bpel\domains\domain_name\config\domain.xml where domain_name is the name of the domain to which you are deploying.	Less than the transaction-timeout value in orion-ejb-jar.xml.	240

Reference: http://docs.oracle.com/cd/B31017_01/integrate.1013/b28981/app_trblshoot.htm