activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3721) StompNIOTransport doStop should check for null before calling selection.stop()
Date Thu, 16 Feb 2012 00:44:59 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQ-3721.
-------------------------------

    Resolution: Fixed

Fix applied in trunk
                
> StompNIOTransport doStop should check for null before calling selection.stop()
> ------------------------------------------------------------------------------
>
>                 Key: AMQ-3721
>                 URL: https://issues.apache.org/jira/browse/AMQ-3721
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: stomp
>    Affects Versions: 5.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Trivial
>             Fix For: 5.6.0
>
>
> The StompNIOTransport calls selection.stop() in doStop and prints an exception stack
trace to the console, the selection object is initialized in initializeStreams which may not
be called if an error occurs as the connection is being establised.  We should add a null
check and not output stack trace data to the console.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message