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 2008/01/31 05:38:08 UTC

DO NOT REPLY [Bug 40213] - Tomcat/JK Software caused connection abort: socket write error

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=40213>.
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=40213


rathinaganesh.tech@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From rathinaganesh.tech@gmail.com  2008-01-30 20:38 -------
(In reply to comment #3)
> By far the #1 cause of this message is a client terminating his/her connection
> (e.g. by closing the browser) while Tomcat is still writing the response.  It's
> usually not fatal by any means, as Tomcat and mod_jk recycle the threads in this
> case.

Hi,

We are having the same issue. We tried it ourself and we did not closeout the
browser or any of the client transactions, but still we see this on our server.
Is there anything we might be missing ? Or Can you please point us towards some
direction. 
We are using JBOSS 4.0.5GA and Mod_JK 1.3.

Thanks,
Ganesh.

-- 
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