Threads are Stuck because Weblogic 10.3 is busy processing on xml.domimpl api

[rash kumar]

Hi,

I have come across a problem in one of our application, in which all the weblogic kernel threads are stuck, after analyzing the thread dumps, i didnt see any race condition, which may have caused the stuck threads neither was there any deadlock condition. All the threads got stuck after exceeding the default timout setting of 600 secs. I have no clue where the things have gone wrong, as this issue seems to appear very rarely and doesnt affect all the clustered servers at the same time. Below is snippet of the thread dump:
[STUCK] ExecuteThread: '401' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x095ff000 nid=0x39e runnable [0x63634000..0x63635970]
java.lang.Thread.State: RUNNABLE
at weblogic.xml.domimpl.ParentNode.nodeListGetLength(ParentNode.java:458)
at weblogic.xml.domimpl.ParentNode.getLength(ParentNode.java:400)
at weblogic.xml.domimpl.ElementBase.getLength(ElementBase.java:24)
at weblogic.wsee.wsdl.WsdlSchema.findImportAndIncludeNodes(WsdlSchema.java:321)
at weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:111)
at weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:73)
at weblogic.wsee.wsdl.WsdlTypes.parse(WsdlTypes.java:165)
at weblogic.wsee.wsdl.WsdlDefinitions.parseChild(WsdlDefinitions.java:520)
at weblogic.wsee.wsdl.WsdlExtensible.parse(WsdlExtensible.java:98)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:468)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:403)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:389)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)
at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:476)
at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)
at com.expressvu.slb.ws.client.EquipmentWS_Impl.<init>(Unknown Source)
at com.expressvu.slb.ws.client.EquipmentWS_Impl.<init>(Unknown Source) .

Please help me out here!!!

Thanks,
Rash.

[sudipto shekhar]

Hi Rash,

Welcome to Java Ranch !!

First you need to find out what exactly is the task/process being executed in the thread. Is it a sql query or any other process that is taking more that expected time to execute ?

For now, you can try increasing the stuck thread timeout seconds to see if the threads becomes unstuck after some time.

Keep posting

[Ramakanta Sahoo]

Hi


java.lang.Thread.State: RUNNABLE
According to what stacktrace you have provided its absolutely fine to have a thread in RUNNABLE state.

You can check out this for more info on analyzing stack traces in weblogic check the Understanding WebLogic Server Stack Traces .

[rash kumar]

rash kumar wrote:Hi,

I have come across a problem in one of our application, in which all the weblogic kernel threads are stuck, after analyzing the thread dumps, i didnt see any race condition, which may have caused the stuck threads neither was there any deadlock condition. All the threads got stuck after exceeding the default timout setting of 600 secs. I have no clue where the things have gone wrong, as this issue seems to appear very rarely and doesnt affect all the clustered servers at the same time. Below is snippet of the thread dump:
[STUCK] ExecuteThread: '401' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x095ff000 nid=0x39e runnable [0x63634000..0x63635970]
java.lang.Thread.State: RUNNABLE
at weblogic.xml.domimpl.ParentNode.nodeListGetLength(ParentNode.java:458)
at weblogic.xml.domimpl.ParentNode.getLength(ParentNode.java:400)
at weblogic.xml.domimpl.ElementBase.getLength(ElementBase.java:24)
at weblogic.wsee.wsdl.WsdlSchema.findImportAndIncludeNodes(WsdlSchema.java:321)
at weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:111)
at weblogic.wsee.wsdl.WsdlSchema.parse(WsdlSchema.java:73)
at weblogic.wsee.wsdl.WsdlTypes.parse(WsdlTypes.java:165)
at weblogic.wsee.wsdl.WsdlDefinitions.parseChild(WsdlDefinitions.java:520)
at weblogic.wsee.wsdl.WsdlExtensible.parse(WsdlExtensible.java:98)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:468)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:403)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:389)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)
at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:476)
at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)


Please help me out here!!!

Thanks,
Rash.

[Ramakanta Sahoo]

Hi Rash,

As I said earlier its absolutely fine to have the thread state as RUNNABLE. You will not have any performance issues. The word [STUCK] tag comes when the process takes 600+secs to complete a task.
You can safely ignore this message.

If you are concerned about some other errors too then put the complete STACKTRACE or thread dump when the issue happens...