You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2013/07/01 14:14:30 UTC

[Bug 55174] New: [jsr 356][websocket] MessageHandler never gets notified again after it throws exception

https://issues.apache.org/bugzilla/show_bug.cgi?id=55174

            Bug ID: 55174
           Summary: [jsr 356][websocket] MessageHandler never gets
                    notified again after it throws exception
           Product: Tomcat 8
           Version: trunk
          Hardware: PC
            Status: NEW
          Severity: major
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: s.boshev@gmail.com

I have a test which adds a MessageHandler which gets notified on text messages.
If its implementation method onMessage(String text) throws some exception (e.g.
runtime exception), this MessageHandler will never ever be notified again for
any new text messages received by the session.

I suppose this happens because the exception actually kills the underlying
thread in which the notification has happened. I think the client side
implementation shall be more robust and expect and be prepared for exceptions
coming from calls to user code.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 55174] [jsr 356][websocket] MessageHandler never gets notified again after it throws exception

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55174

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
                 OS|                            |All

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Thanks for the report.

The javadoc for Endpoint.onError() states it should be called in this case.

trunk has been updated to do this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org