You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/01/11 12:28:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16322133#comment-16322133 ] 

ASF subversion and git services commented on AMQ-6884:
------------------------------------------------------

Commit 4535e8f097c993364026c00ed40777c71a36a6ea in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4535e8f ]

AMQ-6884 - Replacing printStackTrace() with logging statement


> 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)