FTP Adapter Multiplexing to Achieve Load Balancing Does Not Work: BPEL JCA Listener was unable to perform delivery of inbound message to BPEL Process (Doc ID 824276.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager 10g - Version 10.1.3.3 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 31-Oct-2010***
***Checked for relevance on 22-Feb-2013***

Symptoms

File or FTP adapters have been set up in a cluster environment to achieve multiplexing action (round robin polling) by including the following property in the adapter activation agent in bpel.xml:

<activationAgents> 
    <activationAgent className=... 
        <property name="bpelServers"> 
             <server1:port>,<server2:port> 
       </property> 
...

If any of the nodes specified in the "bpelServers" property  is not available at polling time (and therefore the File/FTP adapter too) then the next adapter in the round robin is activated and will pick up the message (file). However under this condition the message processing fails.

An error message like this is registered in the BPEL log file:

<2008-11-06 15:11:33,454> <INFO> <default.collaxa.cube.activation>
<AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - 
successfully completed endpointActivation for portType=Read_ptt, 
operation=Read 
<2008-11-06 15:11:58,544> <ERROR> <default.collaxa.cube.activation> 
<AdapterFramework::Inbound> [Read_ptt::Read(Root-Element)]BPEL JCA Listener 
was unable to perform delivery of inbound message to BPEL Process 
'bpel://localhost/default/FlatStructure~1.0/' due to: Failed to create 
"ejb/collaxa/system/DeliveryBean" bean; exception reported is: 
"javax.naming.CommunicationException: Connection refused [Root exception is 
java.net.ConnectException: Connection refused] 
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:296) 
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51) 
at javax.naming.InitialContext.lookup(InitialContext.java:351) 
at 
com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java: 
279) 
.... 
Caused by: java.net.ConnectException: Connection refused



.

Changes

Setup File or FTP adapter for multiplexing action across a cluster.

Cause

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