BPEL Processes Automatically Redeploying On Restart And Instances Marked As Stale, After Applying 10.1.3.4 MLR 10 (Doc ID 1268941.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.4 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms

If you are seeing the below stated behaviors after applying MLR 10 patchset on top of 10.1.3.4, then you have hit the issue for which the solution is provided in this note:

When you restart the oc4j container on which BPEL Process Manager is deployed or installed, you might notice that the BPEL process which have an deployment plan associated may be redeployed.

The BPEL process, which are redeployed, will have all the previously successfully completed instances marked as stale.

Also this behavior will be intermittent.

Changes

This issue seems to be happening only after applying MLR 10 patchset on top of 10.1.3.4

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