Hassan,
1. Are you accessing an image file when the problem happens ?
2. Is the browser IE ?
3. Does the problem disappear in the first reload after clearing your
browser cache ?
4. Are you using Tomcat in stand alone mode ?
If you answered YES to all the four questions than the problem is probably
due to the lack of support of HTTP Status 304 in Tomcat 3.2 stand alone
server. When the browser discovers that the new image is identical to the
one it has in the cache it simply aborts the connection and uses the cached
value.
The good news is that status 304 is supposed to be supported in Tomcat 4.0.
Tal
> -----Original Message-----
> From: HASSAN,ZAID (Non-A-Australia,ex1)
> [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 21, 2001 4:19 PM
> To: '[EMAIL PROTECTED]'
> Subject: Socket write error
>
>
>
> Hi Folks,
>
> I am also getting the Socket Write error
>
> Ctx(): IOException in R:( + /Template/... + null) Connection aborted by
> peer:socket write error.
>
> Can someone suggest and help here.
>
> Thanks heaps
>
> Zaid
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
