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 16:18:49 UTC

DO NOT REPLY [Bug 39573] - 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


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