100% CPU Utilization Because of Stuck Threads Observed with Apache XML Beans
(Doc ID 1307201.1)
Last updated on AUGUST 01, 2018
Applies to:
Oracle Service Bus - Version 10.3 to 10.3.1 [Release AS10gR3]Information in this document applies to any platform.
Symptoms
There were multiple java stuck threads in the managed servers. This caused the CPU utilization to become 100%
<Error> <WebLogicServer> <S24CJ037> <HOSBPRD_MS2> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1298104919894> <BEA-000337> <[STUCK] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "631" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@b3745", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
org.apache.xmlbeans.impl.store.Locale.exit(Locale.java:2890)
org.apache.xmlbeans.impl.store.Xobj.new_cursor(Xobj.java:1830)
org.apache.xmlbeans.impl.values.XmlObjectBase.newCursor(XmlObjectBase.java:278)
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 |
| References |