JTA transaction is not present or the transaction is not in active state
415791Aug 24 2009 — edited Aug 26 2009Hi All,
we got following error
JTA transaction is not present or the transaction is not in active state
----Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; 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 "240,056". The reason is The execution of this instance "2406" for process "BPEL" 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.
---------------
This issue is happening due to the Invoke is taking more time than time out set intransaction manager.{This invoke is using db adapter}
But i am wondering that increasing the timeout will cause memory issues{Heap Size can only be increased to 3 GB in UNIX)
which paramters affect the invoke performance ?
Any suggestions are appreciated.
Regrds
Arc