Activation Agent in a Cluster will Block Newer Revisions from Activating (Doc ID 729147.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.3 and later
Information in this document applies to any platform.
***Checked for relevance on 31-Oct-2010***


Symptoms

More than 3 revisions in a BPEL cluster using an activation agent will result in 3rd version not becoming active, even if the 3rd version is the default revision.

Example:

If a BPEL process using an FTP adapter is deployed (1.0), and a second is deployed (2.0), the (2.0) process will be the default and will poll as expected.

If a version (3.0) is deployed, the process will cease polling. The following message will be seen in the domain.log file.

<WARN> <default.collaxa.cube.activation> <FTP Adapter: Inbound> PollWork::run exiting, Worker thread will die  

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