You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/01/06 17:15:39 UTC
[jira] [Resolved] (QPIDJMS-146) potential NPE in transport while
establishing SSL connection
[ https://issues.apache.org/jira/browse/QPIDJMS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPIDJMS-146.
------------------------------------
Resolution: Fixed
Resolving as the Appveyor CI build against the 'apache/qpid-jms' mirror on GitHub now seems happy and is the only place this has ever been seen (including other jobs on Appveyor not using the apache account mirror)
> potential NPE in transport while establishing SSL connection
> ------------------------------------------------------------
>
> Key: QPIDJMS-146
> URL: https://issues.apache.org/jira/browse/QPIDJMS-146
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.7.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.8.0
>
>
> There is an issue in the SSL transport, such that it can potentially NPE while establishing the connection, resulting in the attempt hanging.
> The issue looks to occur due to the way we are adding a listener to Netty, hitting some inconsistency in thread safety, coupled with unpredictable threading behaviour at the point the listener is added to a future versus it being completed, topped by Netty swallowing the exception when it is thrown.
> We should adjust the usage of Netty so that we register the listener earlier such that it gives more predictable thead behaviour and avoids possibility of the NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org