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 2015/08/05 18:32:05 UTC

[jira] [Resolved] (AMQ-5919) Clean up printStackTrace statements so that they are logged properly

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

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

> Clean up printStackTrace statements so that they are logged properly
> --------------------------------------------------------------------
>
>                 Key: AMQ-5919
>                 URL: https://issues.apache.org/jira/browse/AMQ-5919
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.11.1
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Minor
>             Fix For: 5.12.0
>
>
> There are a few places in the broker that call printStackTrace() on an exception instead of using the slf4j logger. This stack traces should be logged using the slf4j logger instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)