DO NOT REPLY [Bug 25919] - java.net.SocketException: socket closed

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: java.net.SocketException: socket closed Endpoint ServerSocket

This is a question for the tomcat-user list, not tomcat-dev. Mark > -Original Message- > From: Chirag [mailto:[EMAIL PROTECTED] > Sent: Friday, November 26, 2004 1:15 PM > To: [EMAIL PROTECTED] > Subject: java.net.SocketException: socket closed Endpoint ServerSocke

java.net.SocketException: socket closed Endpoint ServerSocket

: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:450) at

DO NOT REPLY [Bug 25919] - java.net.SocketException: socket closed

gzilla/show_bug.cgi?id=25919 java.net.SocketException: socket closed [EMAIL PROTECTED] changed: What|Removed |Added Summary| java.net.SocketException: |java.net.SocketExc

DO NOT REPLY [Bug 25919] New: - java.net.SocketException: socket closed

gzilla/show_bug.cgi?id=25919 java.net.SocketException: socket closed Summary: java.net.SocketException: socket closed Product: Tomcat 4 Version: 4.1.29 Platform: HP URL: http://www.tellngo.com OS/Version: Windows NT/2K

DO NOT REPLY [Bug 18698] - Exception message in JNDI realm is not "Socket closed" on different ldap implementations

gzilla/show_bug.cgi?id=18698 Exception message in JNDI realm is not "Socket closed" on different ldap implementations [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 18698] New: - Exception message in JNDI realm is not "Socket closed" on different ldap implementations

gzilla/show_bug.cgi?id=18698 Exception message in JNDI realm is not "Socket closed" on different ldap implementations Summary: Exception message in JNDI realm is not "Socket closed" on different ldap implementations Product: Tomcat 4

DO NOT REPLY [Bug 17460] New: - Warp Connector Socket closed

gzilla/show_bug.cgi?id=17460 Warp Connector Socket closed Summary: Warp Connector Socket closed Product: Tomcat 4 Version: 4.1.12 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 13736] - Socket closed unexpectedly

gzilla/show_bug.cgi?id=13736 Socket closed unexpectedly [EMAIL PROTECTED] changed: What|Removed |Added OS/Version|Other |Windows NT/2K --- Additional Co

DO NOT REPLY [Bug 13736] - Socket closed unexpectedly

gzilla/show_bug.cgi?id=13736 Socket closed unexpectedly --- Additional Comments From [EMAIL PROTECTED] 2002-10-18 17:47 --- Try JDK 1.4.1 to see if it helps (worse case, you'll get a nice performance boost), and maybe upgrading to a newer Windows OS if possible (Win 2k has a more reli

DO NOT REPLY [Bug 13736] New: - Socket closed unexpectedly

gzilla/show_bug.cgi?id=13736 Socket closed unexpectedly Summary: Socket closed unexpectedly Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Other Status: NEW Severity: Critical Priority: Other Com

DO NOT REPLY [Bug 13736] - Socket closed unexpectedly

gzilla/show_bug.cgi?id=13736 Socket closed unexpectedly [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

Socket closed

hi there, had this problem: tomcat didn't start reporting a "socket closed"-error (see stack trace of other posted questions). the problem occurred when i tried to port a webapp from my home system (where it was working just fine on linux) to an environment i knew nothing about