BPEL Inbound Adapter Does Not Activate After Server Restart

(Doc ID 1321904.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version and later
Information in this document applies to any platform.
***Checked for relevance on 29-Jan-2013***


In 10g an inbound polling adapter used in BPEL does not start to process messages or files following the start of the server. In the BPEL $ORACLE_HOME/bpel/domains/<your domain>/logs/domain.log or the container log in $ORACLE_HOME/opmn/logs/<BPEL container>.log you will see startup of the JCA for example:

WSDL location='Reader.wsdl'
activation properties={retryInterval=20,
clusterGroupId=ABC12, jca.retry.all=true,

But the adapter never has the polling endpoint activated so is unable to process messages or files.

However, just above this section in the log you might find another polling adapter process whose start up logs indicate successful completion of endpointActivation as in this example:

2011-03-28 20:26:40,487> <INFO>
<AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint -
Creating and initializing inbound JCA endpoint for:
WSDL location='ReadInputParameters.wsdl'
activation properties={portType=DEQUEUE_ptt}

The workaround to get the non-activated adapter endpoint to start processing is to turn the affected BPEL process OFF then back ON from the BPELConsole after startup completes.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms