ORABPEL-05002 Message handle error.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessage"; the exception is: 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 "26090849-BpInv2-BpSeq0.3-3". The reason is The execution of this instance "26090849-BpInv2-BpSeq0.3-3" for process "Test" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
Symptoms :- The error is occurring intermittently in BPEL logs for test domain in the format above.
Cause:- It’s a generic error but in our case it is request time out which is due to inappropriate value of “transaction-config” timeout parameter in transaction-manager.xml in the path below :-
$OH/j2ee/oc4j-soa/config/transaction-manager.xml
Oracle Recommendation :- For us we have defined “600” milliseconds value which seems to be less , it should be increases but on the basis of business requirement.
References :-
1) Section 7.5.1 of http://download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMessage"; the exception is: 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 "26090849-BpInv2-BpSeq0.3-3". The reason is The execution of this instance "26090849-BpInv2-BpSeq0.3-3" for process "Test" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
Symptoms :- The error is occurring intermittently in BPEL logs for test domain in the format above.
Cause:- It’s a generic error but in our case it is request time out which is due to inappropriate value of “transaction-config” timeout parameter in transaction-manager.xml in the path below :-
$OH/j2ee/oc4j-soa/config/transaction-manager.xml
Oracle Recommendation :- For us we have defined “600” milliseconds value which seems to be less , it should be increases but on the basis of business requirement.
References :-
1) Section 7.5.1 of http://download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm
Comments