https://issues.apache.org/bugzilla/show_bug.cgi?id=56416
--- Comment #4 from David <david.lan...@telus.com> --- Mark, On my end we have the following scenario: 1) Start Tomcat 2) Tomcat binds to port and starts loading webapps 3) My web app has a servlet for which load-on-startup is set to True. Tomcat starts to load the servlet. 4) While Tomcat is loading the servlet, client establishes a TCP connection and sends a TCP request. 5) Tomcat is still loading the load-on-startup servlet, so the TCP request sits in the OS buffer. 6) Client gets fed up and closes the TCP connection. 7) Tomcat finishes loading the load-on-startup servlet. 8) Tomcat Acceptor thread starts accepting TCP requests that have built up in the OS buffer 9) Tomcat tries to set various properties on the socket. The problem is that the CLIENT HAS ALREADY CLOSED THE CONNECTION (SEE STEP 7) Result: SocketExceptions in Tomcat log file. Should the above be logged in a separate bug or do you have any other insight. Thanks, David -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org