Hi,

>From the stack trace I see that you're not using Xerces, but rather Sun's
fork of the codebase. Note all the "com.sun.org.apache.*" classes. These
come from Java 6. In particular it looks like XFire is using Sun's StAX
implementation. No equivalent exists in Apache Xerces.

I would suggest that you ask your question on one of the Sun forums.

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org

Bocalinda <bocali...@gmail.com> wrote on 01/30/2009 03:12:52 AM:

> Dear all.
>
> I don't know whether this is the correct mailinglist to post my
> problem, since I am not sure whether it is being caused by Xerces.
> I posted the same message to the Xfire list, just in case.
>
> I'm using Xfire version 1.2.6, Xerces 2.9.1 and Tomcat 6.0.16.
> JDK1.6..0_07
>
> After a while my Tomcat CPU usage goes sky high due to below
> hanging/looping thread:
>
> "http-8081-35" - Thread t...@71
>    java.lang.Thread.State: RUNNABLE
>         at com.sun.org.apache.xerces.internal.impl.
> XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
>         at com.sun.org.apache.xerces.internal.impl.
> XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
>         at com.sun.org.apache.xerces.internal.impl.
> XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:548)
>         at org.codehaus.xfire.soap.handler.ReadHeadersHandler.
> invoke(ReadHeadersHandler.java:44)
>         at org.codehaus.xfire.handler.HandlerPipeline.
> invoke(HandlerPipeline.java:131)
>         at org.codehaus.xfire.transport.DefaultEndpoint.
> onReceive(DefaultEndpoint.java:64)
>         at org.codehaus.xfire.transport.AbstractChannel.
> receive(AbstractChannel.java:38)
>         at org.codehaus.xfire.transport.http.XFireServletController.
> invoke(XFireServletController.java:304)
>         at org.codehaus.xfire.transport.http.XFireServletController.
> doService(XFireServletController.java:129)
>         at org.codehaus.xfire.transport.http.XFireServlet.
> doPost(XFireServlet.java:116)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.
> doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.
> invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.
> invoke(StandardContextValve.java:175)
>         at org.apache.catalina.core.StandardHostValve.
> invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.
> invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.core.StandardEngineValve.
> invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.
> service(CoyoteAdapter.java:286)
>         at org.apache.coyote.http11.Http11Processor.
> process(Http11Processor.java:844)
>         at org.apache.coyote.http11.
> Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.
> run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:619)
>
>    Locked ownable synchronizers:
>         - None

<snip/>

> Any input would be greatly appreciated.
>
> Kind Regards.

Reply via email to