You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/05/13 03:15:00 UTC
DO NOT REPLY [Bug 39573] New: - CPU SPIKING HIGH TO 100%
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39573>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39573
Summary: CPU SPIKING HIGH TO 100%
Product: Tomcat 4
Version: 4.1.0
Platform: Other
OS/Version: AIX
Status: NEW
Severity: blocker
Priority: P1
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: aanand@telcordia.com
CC: aanand@telcordia.com
WE NEED YOUR HELP PLEASE PLEASE !!!, as we are encountering the issue where
the CPU is hiking 100%, when one of the thread in tomcat is getting in the
loop....
[ 12 May 2006 21:02:28,650 ]
[ ERROR ] [Thread-31] - caught throwable: java.net.SocketException: A
connection with a remote s
ocket was reset by that socket.: A connection with a remote socket was reset
by that socket.
java.net.SocketException: A connection with a remote socket was reset by that
socket.: A connection wi
th a remote socket was reset by that socket.
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java(Compiled
Code))
at org.apache.coyote.http11.InternalInputBuffer.fill
(InternalInputBuffer.java:777)
at
org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead
(InternalInputBuff
er.java:807)
at org.apache.coyote.http11.filters.IdentityInputFilter.doRead
(IdentityInputFilter.java:158)
at org.apache.coyote.http11.InternalInputBuffer.doRead
(InternalInputBuffer.java:742)
at org.apache.coyote.Request.doRead(Request.java(Inlined Compiled
Code))
at org.apache.coyote.tomcat4.CoyoteInputStream.readBytes
(CoyoteInputStream.java(Inlined Compile
d Code))
at org.apache.coyote.tomcat4.CoyoteInputStream.read
(CoyoteInputStream.java(Compiled Code))
at org.apache.coyote.tomcat4.CoyoteInputStream.read
(CoyoteInputStream.java(Compiled Code))
at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.readFully
(JAXRPCServletDelegate.java(Co
mpiled Code))
at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doPost
(JAXRPCServletDelegate.java(Compi
led Code))
at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java
(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java
(Compiled Code))
at org.apache.catalina.core.ApplicationFilterChain.access$0
(ApplicationFilterChain.java(Inlined
Compiled Code))
at org.apache.catalina.core.ApplicationFilterChain$1.run
(ApplicationFilterChain.java(Compiled C
ode))
at java.security.AccessController.doPrivileged(Native Method)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 39573] - CPU SPIKING HIGH TO 100%
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39573>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39573
markt@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From markt@apache.org 2006-05-13 14:18 -------
A couple of comments:
1. There is no need to shout.
2. The JAXRPC servlet is sat in the middle of your stack trace. This suggests an
applciation / JAXRPC issue to me. The exception is expected when the client
closes the connection before it has sent all the data. I wonder whether JAXRPC
correctly handles this situation?
3. You have provided no information on how to reproduce this issue.
4. You have reported this issue against a very old version of Tomcat. I would
suggest an upgrade to at least 4.1.31 and better still the latest 5.5.x (not
that I expect it to help with this issue)
5. This question belongs on the users list until such time there is some
evidence of a Tomcat bug.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org