If there is concurrency involved in your scenario, this could be caused by WSCOMMONS-489. There is a known thread safety problem when using Axiom with some StAX implementations (such as SJSXP).
Andreas On Thu, Apr 1, 2010 at 15:31, Jain, Nilendra (Nilendra) <[email protected]> wrote: > Hi, > > We are facing issues with axiom jar 1.2.7. > > Our code's thread which makes a web service client request gets hung and > the stack trace of that thread is as mention below. This hung thread > takes up the CPU.: > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLD > ocumentScannerImpl.java:648) > at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XM > LNSDocumentScannerImpl.java:140) > at > com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStre > amReaderImpl.java:548) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder. > java:506) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1 > 61) > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope( > StAXSOAPModelBuilder.java:156) > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPM > odelBuilder.java:105) > at > org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:53 > ) > at > org.apache.axis2.transport.TransportUtils.createDocumentElement(Transpor > tUtils.java:164) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti > ls.java:112) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti > ls.java:88) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out > InAxisOperation.java:353) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper > ation.java:416) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA > xisOperation.java:228) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 > ) > > > We have observed this pattern at a rate of once per 1000 requests or so. > We have taken the hung threads dump every few seconds or so and have > observed the above stack trace only. > > Any idea about this issue ? We are also unable to interrupt this > thread, so that we can kill it. > > Regards, > Nilendra >
