ORABPEL-05007 - Failed Message Delivery From Inbound JCA Adapters
(Doc ID 1385660.1)
Last updated on MAY 15, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
In the log files there is:
ORABPEL-05007: there is no active transaction while scheduling a message with the dispatcher
And a similar stacktrace:
[2011-11-29T21:08:13.191-05:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.data] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@3660c4d7] [userId: weblogic] [ecid: 860e2cb144ca244c:-74726bb4:133efb3baa8:-8000-00000000000357d7,0] [APP: soa-infra] Error occured when fetch entity manager [[
ORABPEL-05007
could not dispatch message because there is no active transaction.
there is no active transaction while scheduling a message with the dispatcher.
this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer.
Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
at com.collaxa.cube.engine.util.EngineBeanCache.getTransactionSynchronizer(EngineBeanCache.java:172)
at com.collaxa.cube.persistence.dao.impl.jpa.BaseDao.getEntityManager(BaseDao.java:37)
at com.collaxa.cube.persistence.dao.impl.jpa.JpaInvokeMessageDaoImpl.insert(JpaInvokeMessageDaoImpl.java:26)
ORABPEL-05007
could not dispatch message because there is no active transaction.
there is no active transaction while scheduling a message with the dispatcher.
this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer.
Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
at com.collaxa.cube.engine.util.EngineBeanCache.getTransactionSynchronizer(EngineBeanCache.java:172)
at com.collaxa.cube.persistence.dao.impl.jpa.BaseDao.getEntityManager(BaseDao.java:37)
at com.collaxa.cube.persistence.dao.impl.jpa.JpaInvokeMessageDaoImpl.insert(JpaInvokeMessageDaoImpl.java:26)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |