SOA Server Enters FAILED State
(Doc ID 2162866.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Symptoms
Our SOA server intermittently enters FAILED state but appears to keep on processing requests as normal (Health shows OK).
I can't find an explanation for why this is happening.
We restart the managed server and all is well again for a period of time and then the same thing happens again.
ERROR
<Jul 12, 2016 8:40:06 AM AEST> <Emergency> <com.collaxa.cube.engine.dispatch.Sweeper> <BEA-000000> <ORABPELDFW-00001>
<Jul 12, 2016 8:40:06 AM AEST> <Critical> <WebLogicServer> <BEA-000385> <Server health failed. Reason: Health of critical service SOA failed>
<Jul 12, 2016 8:40:06 AM AEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jul 12, 2016 8:40:06 AM AEST> <Critical> <WebLogicServer> <BEA-000385> <Server health failed. Reason: Health of critical service SOA failed>
<Jul 12, 2016 8:40:06 AM AEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
Cause
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
| Symptoms |
| Cause |
| Solution |