Bugs item #573753, was opened at 2002-06-25 14:17
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=104754&aid=573753&group_id=4754
Category: Tapestry
Group: bug
Status: Open
Resolution: None
Priority: 5
Submitted By: joe panico (jpanico)
Assigned to: Howard Lewis Ship (hship)
Summary: client TCP reset causes SocketException
Initial Comment:
When the client issues a TCP RST,
ResponseOutputStreram.flush/forceFlush() raise
SocketException. But this is not really an exceptional
condition. TCP resets are triggered by browsers when
user hits "stop" button or when user transitions to
another page before the currently loading page has been
completely transferred. This produces ugly warnings in
the log which don't really merit a WARN level status.
Fix: trap SocketExceptions in
ResponseOutputStream.flush() and ignore them. Allowing
them to rise and then trapping them in the
AbstractEngine doesn't provide any value to developers,
since there's really nothing to be done about these
anyhow and they don't represent a strong exceptional
condition.
public void flush() throws IOException
{
try
{
if (out != null)
out.flush();
}
catch(SocketException anException)
{
// eat it
}
}
public void forceFlush() throws IOException
{
if (out == null)
open();
this.flush();
}
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=104754&aid=573753&group_id=4754
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
