Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-9398

NullPointerException when connectionKey is not valid

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.17.0
    • camel-atmosphere-websocket
    • None
    • Novice

    Description

      Found a defect in a new feature CAMEL-9393.

      sendMessage in WebsocketProducer should handle the case when websocket is null because of connectionKey is not valid. This fix will be applicable for both send message to singe or to multiple connections.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            davsclaus Claus Ibsen
            pkletsko Pavlo Kletsko
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1h
                1h
                Remaining:
                Remaining Estimate - 1h
                1h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment