FTP Adapter Based Processes Do Not Poll in a Clustered Environment (Doc ID 470716.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.3 and later   [Release: and later ]
Information in this document applies to any platform.
***Checked for relevance on 30-Sep-2010***

Symptoms

After initial deployment in a clustered environment, the cluster is restarted; as consequence the  FTP adapter is not polling for files in any node.  The OPMN log file at $ORACLE_HOME/opmn/logs (typically: default_group~oc4j_soa~default_group~1.log) shows the adapter startup,  but there are no indications of polling. Example:

<2007-11-29 09:17:52,683> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:
process='bpel://localhost/default/TestClusterFTP~2.0/'
domain='default'
WSDL location='ReadFile.wsdl'
portType='Get_ptt'
operation='Get'
activation properties={clusterGroupId=myserver.mycompany.com, portType=Get_ptt}

<2007-11-29 09:17:52,744> <DEBUG> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Creating Delivery Service Load Balance Set for 'localhost' ...

 Nodes have been registered in JGroups as indicated in configuration guide for high availability.

Oracle´┐Ż Application Server Enterprise Deployment Guide
10g Release 3 (10.1.3.3.0)

Part Number E10294-01

Changes

BPEL Active-Active Cluster setup.

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