Exception : connection reset

Hi Everybody,

I have problems  with an orbeon application (2.8) on tomcat 5.5.
The extranet is almost in production and there's no bugs in catalina.out EXCEPT two types of bugs (wich appears very often and that's annoying)

-----------------------------------------------------------------------
2005-11-08 12:46:38,487 ERROR org.orbeon.oxf.pipeline.InitUtils null - Exception with no location data
ClientAbortException:  java.net.SocketException: Connection reset
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
-----------------------------------------------------------------------
2005-11-03 13:58:07,573 ERROR org.orbeon.oxf.pipeline.InitUtils null - Exception at oxf:/oxf/pfc/oxf-rewrite.xsl, line 0, column 0
ClientAbortException:  java.net.SocketException: Connection reset
        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
-----------------------------------------------------------------------

After one day, there is like 50 of these in catalina log.

I've tried to reproduce theses bugs, and that's very easy in fact, i'm just sending a request and just after i click on STOP (red cross) of my browser.
Each time i do this, i have an exception.

Is there a way to eliminate this problem ?

Thanks



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

[hidden email] wrote: Maybe some other users know better, but I have not found any conclusive
information on this. Many people complain about this Tomcat behavior and
log files pollution, but there are not many solutions proposed. I can
see either doing some custom filtering in OPS in OXFServlet, or playing
with log4j settings to log only FATAL messages, except for known OPS
packages which also log ERROR messages.

If filtering this particular exception in OPS makes sense, we should
look into putting an option in OPS. This particular exception is
Tomcat-dependent, so we should probably create an option which takes a
list of exception classes to filter, and then filter based on
getClass().getName().

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws