tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rossen Stoyanchev <rstoyanc...@pivotal.io>
Subject Re: WebSocket strack trace when browser tab closed
Date Fri, 05 Sep 2014 14:39:07 GMT
On Fri, Sep 5, 2014 at 10:26 AM, Mark Thomas <markt@apache.org> wrote:

> On 05/09/2014 15:17, Mark Thomas wrote:
> > On 05/09/2014 15:06, Rossen Stoyanchev wrote:
> >> On Fri, Sep 5, 2014 at 9:33 AM, Mark Thomas <markt@apache.org> wrote:
> >>
> >>> On 05/09/2014 13:46, Rossen Stoyanchev wrote:
> >>>> When a browser tab is a closed a stack trace shows up (see below). I
> >>> think
> >>>> the stack trace means the closing didn't completely cleanly because
> the
> >>>> client didn't wait. Hence probably nothing to worry about, yet the
> logs
> >>>> fill up with stack traces. Is there anything that can be done to
> improve
> >>>> logging in this case and to avoid raising alarm? I thought i'd discuss
> >>> here
> >>>> before opening a ticket.
> >>>
> >>> Tomcat version?
> >>>
> >>
> >> 7.0.54 but also occurs with 8.0.12
> >
> > Thanks. I see what is going on. The IOException is handled but not when
> > it is wrapped with ExecutionException.
> >
> > We should be able to fix that...
>
> I take that back. Tomcat is wrapping the ExecutionException in an
> IOException and is handling the IOException. Tomcat isn't logging this -
> the Endpoint is in the onError() method.
>
> This looks like an application question rather than a Tomcat one.


Ok, that wasn't immediately obvious. Thanks for the quick response. I'll
have a look.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message