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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
