You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "GAURVI JAIN (JIRA)" <ax...@ws.apache.org> on 2014/06/25 20:14:24 UTC

[jira] [Created] (AXIS-2903) Stuck Thread causing High CPU Utilization

GAURVI JAIN created AXIS-2903:
---------------------------------

             Summary: Stuck Thread causing High CPU Utilization
                 Key: AXIS-2903
                 URL: https://issues.apache.org/jira/browse/AXIS-2903
             Project: Axis
          Issue Type: Bug
          Components: WSDL processing
         Environment: Production - Weblogic servers
            Reporter: GAURVI JAIN


Hi,

We are currently seeing the following two types of stuck threads in our
 server logs due to which our server is going to the Unknown state. Since
 this is happening in the production environment it will be great if you
 could provide us some insight -

 1. <Jan 30, 2014 10:30:20 AM EST <Error <WebLogicServer <BEA-000337
 <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default
 (self-tuning)' has been busy for "672" seconds working on the request "Http
 Request: /esmeim/SubmitRemittanceReportByServiceCode.m", which is more than
 the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

 Thread-95 "[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default
 (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON {

 java.lang.String.<init(String.java:197)


 org.apache.axis.message.SAX2EventRecorder.characters(SAX2EventRecorder.java:130)


 org.apache.axis.encoding.DeserializationContextImpl.characters(DeserializationContextImpl.java:890)


 org.apache.xerces.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:456)


 org.apache.xerces.impl.XMLNamespaceBinder.characters(XMLNamespaceBinder.java:608)


 org.apache.xerces.impl.dtd.XMLDTDValidator.characters(XMLDTDValidator.java:835)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleCharacter(XMLDocumentFragmentScannerImpl.java:1089)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1032)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1375)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:331)


 org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:499)


 org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:577)

 org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:146)


 org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1141)

 javax.xml.parsers.SAXParser.parse(SAXParser.java:364)


 org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:238)

 org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:508)

 org.apache.axis.Message.getSOAPEnvelope(Message.java:376)

 org.apache.axis.client.Call.invokeEngine(Call.java:2564)

 org.apache.axis.client.Call.invoke(Call.java:2438)

 org.apache.axis.client.Call.invoke(Call.java:2209)

 org.apache.axis.client.Call.invoke(Call.java:2155)

 org.apache.axis.client.Call.invoke(Call.java:1644)


com.cognos.developer.schemas.bibus._3.CognosReportNetBindingStub.getOutput(CognosReportNetBindingStub.java:7141)

2. ####<Jan 16, 2014 9:33:41 AM EST <Error <WebLogicServer <vgprapp3
 <ESMEIM-MS3 <[ACTIVE] ExecuteThread: '3' for queue:
 'weblogic.kernel.Default (self-tuning)' <<WLS Kernel < <
 <1389882821941 <BEA-000337 <[STUCK] ExecuteThread: '17' for queue:
 'weblogic.kernel.Default (self-tuning)' has been busy for "714" seconds
 working on the request "Http Request:
 /esmeim/SubmitRemittanceReportByServiceCode.m", which is more than the
 configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

 Thread-10339 "[STUCK] ExecuteThread: '17' for queue:
 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended,
 priority=1, DAEMON {

 java.lang.String.toCharArray(String.java:2514)


 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:180)


 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:719)

 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:156)

 org.apache.axis.message.RPCElement.getParams(RPCElement.java:346)

 org.apache.axis.client.Call.invoke(Call.java:2209)

 org.apache.axis.client.Call.invoke(Call.java:2155)

 org.apache.axis.client.Call.invoke(Call.java:1644)


 com.cognos.developer.schemas.bibus._3.CognosReportNetBindingStub.getOutput(CognosReportNetBindingStub.java:7141)




--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


RE: [jira] [Created] (AXIS-2903) Stuck Thread causing High CPU Utilization

Posted by "Yashwanth Rajaram -X (yrajaram - ZENSAR TECHNOLOGIES INC at Cisco)" <yr...@cisco.com>.
Gaurvi, can you check if you have JAXP-RI jar(s) in your class path? If so it is probably not Apach Axis but it is JAXP jars causing this.
If you really have to use JAXP (say jaxp-ri-1.4.2.jar or later) try to see if Woodstox (say wstx-asl-3.2.4.jar or latest) can be used instead. 

Sincerely, Yashwanth

-----Original Message-----
From: GAURVI JAIN (JIRA) [mailto:axis-dev@ws.apache.org] 
Sent: Wednesday, June 25, 2014 11:14 AM
To: java-dev@axis.apache.org
Subject: [jira] [Created] (AXIS-2903) Stuck Thread causing High CPU Utilization

GAURVI JAIN created AXIS-2903:
---------------------------------

             Summary: Stuck Thread causing High CPU Utilization
                 Key: AXIS-2903
                 URL: https://issues.apache.org/jira/browse/AXIS-2903
             Project: Axis
          Issue Type: Bug
          Components: WSDL processing
         Environment: Production - Weblogic servers
            Reporter: GAURVI JAIN


Hi,

We are currently seeing the following two types of stuck threads in our  server logs due to which our server is going to the Unknown state. Since  this is happening in the production environment it will be great if you  could provide us some insight -

 1. <Jan 30, 2014 10:30:20 AM EST <Error <WebLogicServer <BEA-000337  <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default  (self-tuning)' has been busy for "672" seconds working on the request "Http
 Request: /esmeim/SubmitRemittanceReportByServiceCode.m", which is more than  the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

 Thread-95 "[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default  (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON {

 java.lang.String.<init(String.java:197)


 org.apache.axis.message.SAX2EventRecorder.characters(SAX2EventRecorder.java:130)


 org.apache.axis.encoding.DeserializationContextImpl.characters(DeserializationContextImpl.java:890)


 org.apache.xerces.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:456)


 org.apache.xerces.impl.XMLNamespaceBinder.characters(XMLNamespaceBinder.java:608)


 org.apache.xerces.impl.dtd.XMLDTDValidator.characters(XMLDTDValidator.java:835)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleCharacter(XMLDocumentFragmentScannerImpl.java:1089)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1032)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1375)


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:331)


 org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:499)


 org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java:577)

 org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:146)


 org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1141)

 javax.xml.parsers.SAXParser.parse(SAXParser.java:364)


 org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:238)

 org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:508)

 org.apache.axis.Message.getSOAPEnvelope(Message.java:376)

 org.apache.axis.client.Call.invokeEngine(Call.java:2564)

 org.apache.axis.client.Call.invoke(Call.java:2438)

 org.apache.axis.client.Call.invoke(Call.java:2209)

 org.apache.axis.client.Call.invoke(Call.java:2155)

 org.apache.axis.client.Call.invoke(Call.java:1644)


com.cognos.developer.schemas.bibus._3.CognosReportNetBindingStub.getOutput(CognosReportNetBindingStub.java:7141)

2. ####<Jan 16, 2014 9:33:41 AM EST <Error <WebLogicServer <vgprapp3
 <ESMEIM-MS3 <[ACTIVE] ExecuteThread: '3' for queue:
 'weblogic.kernel.Default (self-tuning)' <<WLS Kernel < <
 <1389882821941 <BEA-000337 <[STUCK] ExecuteThread: '17' for queue:
 'weblogic.kernel.Default (self-tuning)' has been busy for "714" seconds  working on the request "Http Request:
 /esmeim/SubmitRemittanceReportByServiceCode.m", which is more than the  configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

 Thread-10339 "[STUCK] ExecuteThread: '17' for queue:
 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended,  priority=1, DAEMON {

 java.lang.String.toCharArray(String.java:2514)


 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:180)


 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:719)

 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:156)

 org.apache.axis.message.RPCElement.getParams(RPCElement.java:346)

 org.apache.axis.client.Call.invoke(Call.java:2209)

 org.apache.axis.client.Call.invoke(Call.java:2155)

 org.apache.axis.client.Call.invoke(Call.java:1644)


 com.cognos.developer.schemas.bibus._3.CognosReportNetBindingStub.getOutput(CognosReportNetBindingStub.java:7141)




--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org