Managed Server goes to Failed State due to Deadlock
Last updated on DECEMBER 11, 2017
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A managed server Instance is going to failed state due to the below errors:
<Jun 5, 2017 5:53:10 AM EDT> <Critical> <Health> <BEA-310006> <Critical subsystem core has failed. Setting server state to FAILED.
Reason: Thread deadlock detected>
<Jun 5, 2017 5:53:10 AM EDT> <Critical> <WebLogicServer> <BEA-000385> <Server health failed. Reason: health of critical service 'core' failed>
<Jun 5, 2017 5:53:10 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Jun 5, 2017 5:53:10 AM EDT> <Error> <> <BEA-000000> <THREAD DUMP from JVM taken at 'Mon Jun 5 05:53:10 2017'
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