Activation Agent will not invoke default process In Cluster Environment
Last updated on NOVEMBER 03, 2016
Applies to:Oracle(R) BPEL Process Manager - Version: 10.1.3.3
This problem can occur on any platform.
If multiple versions of a BPEL process are deployed in a cluster, the activation agent will not always invoke the default process.
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 process.
While Polling in a cluster, the (1.0) process is invoked rather than the default version (2.0).
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