Getting JSP error when rolling over an image

[Patrick Valiquette]

Hi,

Could anyone give us a clue on this one?
We're getting the following error while doing a rollover on an image on a
web page using JSP and Tomcat 3.3 :

ErrorHandler: Error loop for R( /clients +
/CSRS/images/menu/commissaires_over.gif + null) error
java.net.SocketException: Connection reset by peer: socket write error
Ctx(/clients) : IOException in R( /clients +
/CSRS/images/menu/accueil_over.gif + null) - java.net.SocketException:
Connection reset by peer: socket write error

The "/client" part is the application's context (stored in a variable) wich
is concatenated with the image path. But why there is a "+ null" added at
the end eludes us.
The error happens when a "quick" rollover is done on any image on the menu.
I say "quick" because, strangely enough, rolling over the menu's images
"slowly" doesn't generate this error.

Here is a sample HTML tag containing the event handler :

<A HREF="../commissaires/index.jsp"
onMouseOver="commis.src='../images/menu/commissaires_over.gif';"
onMouseOut="commis.src='../images/menu/commissaires_select.gif';"><IMG
src="../images/menu/commissaires_select.gif" border=0 name="commis"></A>

In fact, as you can see, we're not even concatenating the app's context
since we're using relative paths to change the image's source. So why would
Tomcat add the context before the path, and then "+ null" at the end?!
We are not using a web server while developping, only Tomcat. The menu is
hosted in a separate page (menu.jsp) which is included into all the site's
pages using <jsp:include>.

Thank you for any lead you can provide.

Here is the complete error message :

ErrorHandler: Error loop for R( /clients +
/CSRS/images/menu/commissaires_over.gif + null) error
java.net.SocketException: Connection reset by peer: socket write error
Ctx(/clients) : IOException in R( /clients +
/CSRS/images/menu/accueil_over.gif + null) - java.net.SocketException:
Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:126)
at
org.apache.tomcat.modules.server.Http10.sendHeaders(Http10.java:404)
at
org.apache.tomcat.modules.server.HttpResponse.endHeaders(Http10Interceptor.j
ava:474)
at
org.apache.tomcat.core.OutputBuffer.realWriteBytes(OutputBuffer.java:176)
at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360)
at
org.apache.tomcat.core.OutputBuffer.flush(OutputBuffer.java:318)
at
org.apache.tomcat.core.OutputBuffer.close(OutputBuffer.java:305)
at org.apache.tomcat.core.Response.finish(Response.java:271)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:838)
at
org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Http10I
nterceptor.java:176)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:516)
at java.lang.Thread.run(Thread.java:536)

________________
Patrick Valiquette