Fault Instances Retry Continuously After SOA Server Restart
(Doc ID 2284226.1)
Last updated on SEPTEMBER 03, 2020
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Faulted instances are auto retrying continuously even though the auto-recovery is disabled. This is happening only when fault policy files are part of Oracle Metadata Services (MDS) Repository shared area. When it is being used a fault policy files locally it is working as expected. This is causing customer's log files filled up and server performance issue.
The issue can be reproduced at will with the following steps:
1. Created a simple composite, the bpel basically invokes an OSB service. The composite is set to apply the fault policy ‘RetryAndManualRecoveryFaultPolicy’ which does a retry for 3 times for any remote fault and goes to human intervention.
2. The OSB service calls a dummy business service which throws an error that is handled in the OSB service and sent as remote fault back to BPEL.
3. The retry happens for 3 times and flow state is set to ‘Recovery Required’.
4. The SOA servers are bounced and post the restart all the instances that are in recovery does a continuous retry of the instance.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document