My Oracle Support Banner

Error Committing Transaction with ORABPEL-05007 (Doc ID 2611199.1)

Last updated on JANUARY 08, 2024

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


Application cannot run with the below error :

< current transaction status is non-active: 1>

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).

an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "ORABPEL-00000

Exception not handled by the Collaxa Cube system.
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "javax.ejb.TransactionRolledbackLocalException: Error committing transaction:; nested exception is: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Internal error: Cannot obtain XAConnection Connection has been administratively destroyed by console/admin command. Reconnect. java.lang.Exception: It was destroyed at Tue Nov 12 08:57:32 ICT 2019

and after restarting SOA server the issue is resolved.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.