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/08/08 17:07:19 UTC
DO NOT REPLY [Bug 40213] New: - 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
Summary: Tomcat/JK Software caused connection abort: socket write
error
Product: Tomcat 5
Version: 5.5.17
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: normal
Priority: P2
Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: peter.shipstone@computeach.co.uk
Tomcat keeps throwing the following warning within it log files. I'm not sure
if this is the cause of our tomcat server dying sporadically with no real
error message being reported but I would like to clear the issue. This error
has only been reported since upgrading from an earlier version of Tomcat.
08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
at org.apache.jk.common.JkInputStream.endMessage
(JkInputStream.java:112)
at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
at org.apache.coyote.Response.action(Response.java:182)
at org.apache.coyote.Response.finish(Response.java:304)
at org.apache.jk.server.JkCoyoteHandler.invoke
(JkCoyoteHandler.java:204)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
(ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
--
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 40213] - Tomcat/JK Software caused connection abort: socket write error
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=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
------- Additional Comments From peter.shipstone@computeach.co.uk 2006-08-08 15:11 -------
(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files. I'm not
sure
> if this is the cause of our tomcat server dying sporadically with no real
> error message being reported but I would like to clear the issue. This
error
> has only been reported since upgrading from an earlier version of Tomcat.
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write
error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
> at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> at org.apache.coyote.Response.action(Response.java:182)
> at org.apache.coyote.Response.finish(Response.java:304)
> at org.apache.jk.server.JkCoyoteHandler.invoke
> (JkCoyoteHandler.java:204)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
> at org.apache.jk.common.ChannelSocket.processConnection
> (ChannelSocket.java:684)
> at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
> (ChannelSocket.java:876)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files. I'm not
sure
> if this is the cause of our tomcat server dying sporadically with no real
> error message being reported but I would like to clear the issue. This
error
> has only been reported since upgrading from an earlier version of Tomcat.
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write
error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
> at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> at org.apache.coyote.Response.action(Response.java:182)
> at org.apache.coyote.Response.finish(Response.java:304)
> at org.apache.jk.server.JkCoyoteHandler.invoke
> (JkCoyoteHandler.java:204)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
> at org.apache.jk.common.ChannelSocket.processConnection
> (ChannelSocket.java:684)
> at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
> (ChannelSocket.java:876)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files. I'm not
sure
> if this is the cause of our tomcat server dying sporadically with no real
> error message being reported but I would like to clear the issue. This
error
> has only been reported since upgrading from an earlier version of Tomcat.
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write
error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
> at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> at org.apache.coyote.Response.action(Response.java:182)
> at org.apache.coyote.Response.finish(Response.java:304)
> at org.apache.jk.server.JkCoyoteHandler.invoke
> (JkCoyoteHandler.java:204)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
> at org.apache.jk.common.ChannelSocket.processConnection
> (ChannelSocket.java:684)
> at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
> (ChannelSocket.java:876)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
Also, not sure if this is connected but the JK Connector is logging errors:
[Tue Aug 08 13:25:51 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 13:32:12 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002745
[Tue Aug 08 13:45:24 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002745
[Tue Aug 08 13:56:29 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002745
[Tue Aug 08 14:00:36 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:00:36 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:07:21 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:07:21 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:15:37 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:15:37 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:18:03 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:20:44 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:20:44 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:21:29 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002745
[Tue Aug 08 14:47:54 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:47:54 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:50:05 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:50:05 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:50:31 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 14:50:31 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 14:53:11 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 15:00:18 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 15:33:04 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 15:33:54 2006] [error] jk_isapi_plugin.c (549):
HSE_REQ_SEND_RESPONSE_HEADER failed
[Tue Aug 08 15:33:54 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002746
[Tue Aug 08 15:57:09 2006] [error] jk_isapi_plugin.c (639): WriteClient failed
with 00002745
[Tue Aug 08 15:57:09 2006] [error] jk_isapi_plugin.c
--
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 40213] - Tomcat/JK Software caused connection abort: socket write error
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=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
DO NOT REPLY [Bug 40213] - Tomcat/JK Software caused connection abort: socket write error
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=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
------- Additional Comments From mgreca@capes.gov.br 2006-08-16 14:14 -------
I have the same problem. Any one knows how do i fix?
(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files. I'm not sure
> if this is the cause of our tomcat server dying sporadically with no real
> error message being reported but I would like to clear the issue. This error
> has only been reported since upgrading from an earlier version of Tomcat.
>
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
> at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
> at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
> at org.apache.coyote.Response.action(Response.java:182)
> at org.apache.coyote.Response.finish(Response.java:304)
> at org.apache.jk.server.JkCoyoteHandler.invoke
> (JkCoyoteHandler.java:204)
> at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
> at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
> at org.apache.jk.common.ChannelSocket.processConnection
> (ChannelSocket.java:684)
> at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
> (ChannelSocket.java:876)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
--
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 40213] - Tomcat/JK Software caused connection abort: socket write error
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=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
yoavs@computer.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From yoavs@computer.org 2006-12-24 19:48 -------
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.
--
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 40213] - Tomcat/JK Software caused connection abort: socket write error
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=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
markt@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
------- Additional Comments From markt@apache.org 2008-02-01 13:15 -------
A firewall, a faulty network connection, a bad NIC, the list goes on. This is a
network issue, not a Tomcat issue.
--
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