Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3648

Improve logging in unhandled websocket exceptions

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.1.0.Final
    • Fix Version/s: 9.0.0.Alpha1
    • Component/s: Web Sockets
    • Labels:
      None

      Description

      Currently, if an exception is thrown in an @OnMessage method in a websocket server, the exception is not printed anywhere. It would be ideal to catch this exception and report it back to the end user (developer) so that they can be aware of their runtime issues and fix them.

      At least from my experience, these are development problems, and are indicative of something wrong rather than an actual exception.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                swd847 Stuart Douglas
                Reporter:
                meetoblivion John Ament
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: