You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/09/21 12:15:00 UTC
[jira] [Updated] (AMQ-6820) NIO transport should properly handle
ClosedChannelException
[ https://issues.apache.org/jira/browse/AMQ-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon updated AMQ-6820:
----------------------------------------
Fix Version/s: 5.16.0
> NIO transport should properly handle ClosedChannelException
> -----------------------------------------------------------
>
> Key: AMQ-6820
> URL: https://issues.apache.org/jira/browse/AMQ-6820
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.15.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.15.1, 5.16.0
>
>
> The NIO transport does not properly handle a ClosedChannelException when it happens inside the SelectorSelection class. Instead of properly disposing of the transport it calls System.out.println() for the exception and keeps the transport alive. This caused a NPE later when the enable() method was called because the SelectionKey was null. The fix is to call onError() when the ClosedChannelException occurs so things get cleaned up and logged properly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)