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 2018/01/11 12:29:00 UTC

[jira] [Resolved] (AMQ-6884) NIO SelectorWorker should use logger instead of printStackTrace

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

Christopher L. Shannon resolved AMQ-6884.
-----------------------------------------
    Resolution: Fixed

> NIO SelectorWorker should use logger instead of printStackTrace
> ---------------------------------------------------------------
>
>                 Key: AMQ-6884
>                 URL: https://issues.apache.org/jira/browse/AMQ-6884
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.15.2
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Minor
>             Fix For: 5.16.0, 5.15.3
>
>
> There are a couple of spots in the SelectorWorker class where exceptions are printed using printStackTrace() instead of logged properly. They should be logged properly using SLF4J and not sent to stout so users can control the output.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)