Dear all,
We are using Tomcat 3.2.1 with Microsoft IIS4 and IE5. After upgrading from
Tomcat version 3.1 to version 3.2.1, we are receiving the SocketException
and messages described below. We are trying to import a JavaScript-file,
generated by Tomcat (via JSP), in an HTML-file. Each time a
JavaScript-function is called, the SocketException occurs. Does anyone know
what the problem is here? Is this a Tomcat-bug or are we doing something
wrong? Any help would be appreciated!!!
This is what we are trying:
HTML <-- JS-file (import) <-- |via Tomcat 3.2| <-- JSP-file
This is what we are getting:
SocketException:
----------------
2001-03-27 01:54:19 - ContextManager: SocketException reading request,
ignored - java.net.SocketException: Connection reset by peer: JVM_recv in
socket input stream read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
at
org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapter.java:115)
at
org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInputStream.java:106)
at
org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputStream.java:128)
at
javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
at
org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpRequestAdapter.java:129)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:195)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)
Other problems:
---------------
2001-03-27 01:54:19 - Ctx( /op0010 ): 404 R( /op0010 + /imap/map/none +
null) null
2001-03-27 01:54:09 - Ctx( ): 400 R( /) null
The SocketException appears only once or twice after restarting Tomcat. The
other two problems appear each time the JavaScript-function is triggered in
the webpage (which is in an onMouseOver-event, thus about 20 times each
second!!!)
Regards,
Joeri
