You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/07 10:50:10 UTC
[jira] [Commented] (CAMEL-9398) NullPointerException when
connectionKey is not valid
[ https://issues.apache.org/jira/browse/CAMEL-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044671#comment-15044671 ]
ASF GitHub Bot commented on CAMEL-9398:
---------------------------------------
GitHub user pkletsko opened a pull request:
https://github.com/apache/camel/pull/716
[CAMEL-9398] NullPointerException when connectionKey is not valid
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pkletsko/camel CAMEL-9398
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/716.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #716
----
commit f43c5359c64992c7f2dc011e38bb799f7a2a7f69
Author: Pavlo Kletsko <pk...@gmail.com>
Date: 2015-12-07T09:49:08Z
[CAMEL-9398] NullPointerException when connectionKey is not valid
----
> NullPointerException when connectionKey is not valid
> ----------------------------------------------------
>
> Key: CAMEL-9398
> URL: https://issues.apache.org/jira/browse/CAMEL-9398
> Project: Camel
> Issue Type: Bug
> Components: camel-atmosphere-websocket
> Reporter: Pavlo Kletsko
> Fix For: 2.17.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)