> -----Original Message----- > From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Sent: Sunday, December 12, 2010 10:23 PM > To: users@tomcat.apache.org > Subject: Re: Tomcat Jakarta 1.2.31 ISAPI Reconnector incorrectly > sending Content body with HTTP 304 Status > > 10054 is a winsock error code, so in this case we got "WSAECONNRESET". > Citing from > http://msdn.microsoft.com/en-us/library/ms740668%28v=vs.85%29.aspx: > > > Connection reset by peer. > > An existing connection was forcibly closed by the remote host. > This > normally results if the peer application on the remote host is > suddenly stopped, the host is rebooted, the host or remote network > interface is disabled, or the remote host uses a hard close (see > setsockopt for more information on the SO_LINGER option on the remote > socket). This error may also result if a connection was broken due to > keep-alive activity detecting a failure while one or more operations are in progress. > Operations that were in progress fail with WSAENETRESET. Subsequent > operations fail with WSAECONNRESET.
Thanks. I didn't know that 10054 was meant as a winsock error code, although I have seen the 10054 often enough in other (non-http) applications using Winsock. :) Thanks, and Merry Christmas --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
