My Oracle Support Banner

Adapter Messages Polled by Mediator not Handed off to BPEL (Doc ID 1392594.1)

Last updated on FEBRUARY 22, 2019

Applies to:

Oracle SOA Suite - Version to [Release 11gR1]
Information in this document applies to any platform.


SOA and higher

We have 3 composite application:

Queue -> (JMS/AQAdapter -> Mediator -> BPEL -> DBAdapter) -> (Mediator) ->
(Mediator -> BPEL -> DBAdapter)

Where... ( ) mean a Composite.

Following is the flow:

1) Data to be published from one system to one (or many) other systems is written to a staging table.

2) That staging table has a trigger that, on insert, enqueues an AQ message to an AQ queue with a primary key for the data that was just written.

3) A SOA composite has an AQ/JMS adapter listening to the queue, dequeues the message and passes it on to a BPEL process which then reads the appropriate data from the staging table (based on the primary key from the AQ message), and publishes that data out to other interested systems.

What's happening is that the AQ message is being enqueued by the database trigger, the AQ listener from the composite is successfully dequeing that message, but then nothing else is happening - the AQ/JMS adapter is not passing the dequeued message on to the BPEL process in the same composite.

Also there no error in the log files that may indicate a potential failure from any component.

After apply <Patch 12573835> BPEL Messages were rejected and transaction rolled back due to Message handling errors while trying to create and invoke BPEL instances, as the
schema validation fails. Following exception is seen:

<BEA-000000> <Failed to handle dispatch message ... exception ORABPEL-05002

Message handle error.
error while attempting to process the message
"com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the
reported exception is: Could not initialize variable.
An error occurs while initializing BPEL variable getFundingNumberInput; the
schema processor cannot find the element
{}InputParameters in the following schemas:
The XSD element on which the variable was based was not properly defined in
XSD or the WSDL.
Ensure that the element named in the error message is valid in the XSD or the


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.