I'm not sure anyone here can. Tomcat is good at recovering from a
client abort -- they happen a lot for all sorts of reasons. Sounds like
the ARS Mid-Tier (what ever that is) is at fault and doesn't deal with
rejection very well. Have you contacted the company regarding this?
ratul
Tomcat stops after client browser in cancelled midway when it is loading.
The localhost.log gives :
ClientAbortException: java.net.SocketException: Connection reset by peer:
socket write error
From: ratul banerjee [mailto:[EMAIL PROTECTED]
Tomcat stops after client browser in cancelled midway when it
is loading.
That sounds like the webapp you're running does something inappropriate when it
gets an exception. Check it for nasties like System.Exit() calls.
The localhost.log gives
Hi Peter,
Could not find anything close to that
To add something more,this is happening in case of client browser that is
requesting a big download and midway during the search the client browser is
closed.
On 3/18/08, Peter Crowther [EMAIL PROTECTED] wrote:
From: ratul banerjee
From: ratul banerjee [mailto:[EMAIL PROTECTED]
Could not find anything close to that
OK.
To add something more,this is happening in case of client
browser that is
requesting a big download and midway during the search the
client browser is closed.
Is the download static content, or is
Is the download static content, or is it generated? If it's generated,
what's the code that generates it?
The download content is generated.
It is generated through the ARS Mid-Tier.
Also... could you give us some more details on OS, Tomcat version, whether
it's standalone or fronted by Apache
