Right after installing the ‘ora’ example application for Tomcat, I surfed to http://localhost:8080/ora no problem, then clicked on Chapter 5, Current Date/Time example. Long delay, then finally the date and time are displayed. But in my Tomcat startup console window, I see:
2000-12-29 10:18:37 - Ctx( ): IOException in: R( + /tomcat-power.gif + null) socket write error (code=10053) 2000-12-29 10:18:37 - Ctx( ): IOException in: R( + /index.html + null) socket write error (code=10053) Do I have an install problem? |
| Answer: First, the delay you see the first time you access a JSP page is the time it takes to convert the JSP page into a servlet class file. It only happens the first time, and when you change the JSP page.The error message means that Tomcat could not send the complete response to the browser, because the browser has already closed its connection.As far as I know, this only happen with Internet Explorer (IE). IE seems to close the connection before it has received the complete response when it asks for a resource it already has in its cache. So the first time you load the Tomcat index page, everything is fine. But from then on, both the index.html and the image file are in IE’s cache, and you see this message. It doesn’t cause any problems though, so you can just ignore it. Rumor has it that this problem can be fixed with the latest patches for IE, at least on some Windows platforms. You can also reduce the log level for the Tomcat server so it doesn’t print these error messages. See the Tomcat configuration documents for details. If you use Netscape instead, you’ll notice that it behaves according to the HTTP spec, so you don’t get this message. |
Hans Bergsten
Software Adventures
