This has come up a couple of times. Is there no way of disabling the stack trace? Considering that this is more of a notification, should it not just result in a callback to implementors, rather than being printed to screen like an application-level failure?
On 1/23/10, Emmanuel Lecharny <[email protected]> wrote: > Ted Yu a écrit : >> Hi, >> I saw this snippet in our server log many times: >> >> > <snip/> >> java.io.IOException: Connection reset by peer >> > </snip> > >> If someone has seen such stack trace, please share how to fix the problem. >> > Very simple : stop accepting clients who evily disconnect without notice > ! Bad, bad clients ... I *always* close a socket correctly, never > slamming the door, even if my computer stops because of a power shutdown... > > More serioulsy, it's just an information that a client has quit > brutally. There is nothing to fix here, except logging less. > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.nextury.com > > >
