DO NOT REPLY [Bug 34434] New: - ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error

2005-04-13 Thread bugzilla
/show_bug.cgi?id=34434 Summary: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error Product: Tomcat 5 Version: 5.5.7 Platform: Other OS/Version: Windows 2000 Status: NEW

DO NOT REPLY [Bug 34434] - ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error

2005-04-13 Thread bugzilla
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=34434. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 34434] - ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error

2005-04-13 Thread bugzilla
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=34434. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 34434] - ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error

2005-04-13 Thread bugzilla
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=34434. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 34170] - Connection reset by peer exception while performing basic authentication (db connection pool not being used)

2005-03-31 Thread bugzilla
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=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 34170] New: - Connection reset by peer exception while performing basic authentication (db connection pool not being used)

2005-03-24 Thread bugzilla
/show_bug.cgi?id=34170 Summary: Connection reset by peer exception while performing basic authentication (db connection pool not being used) Product: Tomcat 5 Version: 5.5.7 Platform: Macintosh OS/Version: other Status: NEW

DO NOT REPLY [Bug 34170] - Connection reset by peer exception while performing basic authentication (db connection pool not being used)

2005-03-24 Thread bugzilla
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=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 34170] - Connection reset by peer exception while performing basic authentication (db connection pool not being used)

2005-03-24 Thread bugzilla
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=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 28790] - connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 mod_jk2

2004-12-13 Thread bugzilla
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=28790. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 28790] - connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 mod_jk2

2004-11-05 Thread bugzilla
/show_bug.cgi?id=28790 connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 mod_jk2 --- Additional Comments From [EMAIL PROTECTED] 2004-11-05 18:37 --- We are having the same error with Linux and JBoss 3.2.5 mod_jk: Error flushing [Fri Nov 05 11:21:31 2004] [error

DO NOT REPLY [Bug 28790] - connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 mod_jk2

2004-08-13 Thread bugzilla
/show_bug.cgi?id=28790 connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 mod_jk2 [EMAIL PROTECTED] changed: What|Removed |Added Summary|connection reset

DO NOT REPLY [Bug 29240] - java.sql.SQLException: Io exception: Connection reset by peer: socket write error

2004-05-27 Thread bugzilla
/show_bug.cgi?id=29240 java.sql.SQLException: Io exception: Connection reset by peer: socket write error [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 29240] New: - java.sql.SQLException: Io exception: Connection reset by peer: socket write error

2004-05-26 Thread bugzilla
/show_bug.cgi?id=29240 java.sql.SQLException: Io exception: Connection reset by peer: socket write error Summary: java.sql.SQLException: Io exception: Connection reset by peer: socket write error Product: Tomcat 4 Version: 4.1.24 Platform

DO NOT REPLY [Bug 28790] New: - connection reset by peer and ajp13.service() ajpGetReply recoverable error 3

2004-05-05 Thread bugzilla
/show_bug.cgi?id=28790 connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 Summary: connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 Product: Tomcat 4 Version: 4.1.29 Platform: PC OS

DO NOT REPLY [Bug 28790] - connection reset by peer and ajp13.service() ajpGetReply recoverable error 3

2004-05-05 Thread bugzilla
/show_bug.cgi?id=28790 connection reset by peer and ajp13.service() ajpGetReply recoverable error 3 --- Additional Comments From [EMAIL PROTECTED] 2004-05-05 19:46 --- The java.io.IOException: Connection reset by peer instances in our servlet logs occur when we attempt to write to the output

Tomcat : Connection reset by peer: socket write error

2003-12-29 Thread Carlos Fernandez
With Win32 : Tomcat 3.2.x + Apache 1.3.26 + mod_jk port 80 Tomcat 3.3.x + Apache 1.3.26 + mod _jk port 80 Tomcat 5.0.16 standalone port 8080 : I am getting an exception(socket write error) from a native method(socketWrite) in SocketOutputStream saying Connection reset by peer: socket

DO NOT REPLY [Bug 7714] New: - java.net.SocketException: Connection reset by peer: socket write error

2002-04-03 Thread bugzilla
/show_bug.cgi?id=7714 java.net.SocketException: Connection reset by peer: socket write error Summary: java.net.SocketException: Connection reset by peer: socket write error Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version

DO NOT REPLY [Bug 7714] - java.net.SocketException: Connection reset by peer: socket write error

2002-04-03 Thread bugzilla
/show_bug.cgi?id=7714 java.net.SocketException: Connection reset by peer: socket write error [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

RE: Connection reset by peer

2001-12-11 Thread GOMEZ Henri
: Re: Connection reset by peer Hello, I had the same problem with tomcat in windows environment. Its just that when ever your connection between Tomcat and its client (mostly a web browser) breaks (may be due to pressing stop button in the browser or due to any other reason) it throws exception

Connection reset by peer

2001-12-10 Thread Renato
Hi all, I was looking through tomcat's log ( tomcat 3.2.4 + mod_jk under Red Hat 7.2 + Sun JVM 1.3.1_01 ) and I saw a lot of messages like this: java.net.SocketException: Connection reset by peer: Connection reset by peer at java.net.SocketInputStream.socketRead(Native Method

Re: Connection reset by peer

2001-12-10 Thread Muhammad Ali Siddiqui
: [EMAIL PROTECTED] Sent: Monday, December 10, 2001 5:26 PM Subject: Connection reset by peer Hi all, I was looking through tomcat's log ( tomcat 3.2.4 + mod_jk under Red Hat 7.2 + Sun JVM 1.3.1_01 ) and I saw a lot of messages like this: java.net.SocketException: Connection reset by peer

Re: Connection reset by peer

2001-12-10 Thread Renato
It looks that this error however is happening at the connector pool level. I see other 'connection reset by peer' errors but they have different stacks. This one looks more critical. It might also a bug in the JVM. Hello, I had the same problem with tomcat in windows environment. Its just