Fault Policy Does Not Complete and BPEL Wait Activities Do Not Expire on 10.1.3.5.1 Following Container Stop and Start
Last updated on NOVEMBER 03, 2016
Applies to:Oracle(R) BPEL Process Manager - Version 10.1.3.5.0 and later
Information in this document applies to any platform.
You have configured a BPEL process using the Fault Policy Framework setup to perform multiple retries for example. The first and second retries execute, then the container is stopped using OPMNCTL shutdown and then started again, the next retry is never attempted. The process just remains in open.running forever.
This has been seen in 10.1.3.5.1 OC4J both when the retry interval had already expired before the container restart and also seen when the retry interval had not yet expired after the container restart.
If a stop and start of the container are not done, all of the retries execute through to the last one.
Also if there are pending BPEL Wait activities and the container is stopped and started these will not expire following the restart.
This is not a problem in versions prior to 10.1.3.5.1
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