Skip to main content

Possible bug with Xerces implementation Sun JDK 1.6

No replies
Joined: 2006-08-20

Hi All,

I'm running Tomcat 6.0.16 on Sun JDK 1.6.0_07 and I am seeing regular hangups.
After several thread dumps, I noticed there are 1-2 threads that keep running continuously and take up 100% of CPU time. Please see below for their stacktrace:

"http-8081-35" - Thread t@71
java.lang.Thread.State: RUNNABLE
at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(
at org.codehaus.xfire.handler.HandlerPipeline.invoke(
at org.codehaus.xfire.transport.DefaultEndpoint.onReceive(
at org.codehaus.xfire.transport.AbstractChannel.receive(
at org.codehaus.xfire.transport.http.XFireServletController.invoke(
at org.codehaus.xfire.transport.http.XFireServletController.doService(
at org.codehaus.xfire.transport.http.XFireServlet.doPost(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
at org.apache.catalina.core.StandardWrapperValve.invoke(
at org.apache.catalina.core.StandardContextValve.invoke(
at org.apache.catalina.core.StandardHostValve.invoke(
at org.apache.catalina.valves.ErrorReportValve.invoke(
at org.apache.catalina.core.StandardEngineValve.invoke(
at org.apache.catalina.connector.CoyoteAdapter.service(
at org.apache.coyote.http11.Http11Processor.process(
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(

Locked ownable synchronizers:
- None

I don't see any of those problems when using Tomcat 5.5 with JDK 1.5.
I even tried Tomcat 6 with JDK 1.5, and it works as a charm as well.
This makes me conclude that the problem resides in JDK 1.6.
I have to say that I am not a programmer, and however I took a look at the Sun Xerces source code, I'm unable to tell where the problem lies.

I hope someone will be able to give me some input.

Thanks in advance.