Oracle SOA Suite (MOSC)

MOSC Banner

Exception: ORABPEL-05007

edited Nov 7, 2019 2:35AM in Oracle SOA Suite (MOSC) 4 commentsAnswered

Hello,

can you please help with this issue:

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

Handled As: com.collaxa.cube.CubeException

]

** Cikey: 1181188

** FlowId: 980297

** Current Activity Key: 1181188-BpRpl3-BpSeq22.10-4

** Current Activity Label: ReplyGetInfoByAccNew

** ComponentDN: default/AmluServicesNew!1.0*soa_f833e5d3-e44b-45e7-9c95-5549ed99f8f0/AmluServicesN

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center