You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Martyn Taylor (JIRA)" <ji...@apache.org> on 2016/01/22 10:24:39 UTC

[jira] [Resolved] (ARTEMIS-296) Do not print stack trace on BridgeDisconnect

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

Martyn Taylor resolved ARTEMIS-296.
-----------------------------------
       Resolution: Fixed
         Assignee: Martyn Taylor
    Fix Version/s: 1.2.0

> Do not print stack trace on BridgeDisconnect
> --------------------------------------------
>
>                 Key: ARTEMIS-296
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-296
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Martyn Taylor
>            Assignee: Martyn Taylor
>             Fix For: 1.2.0
>
>
> A bridge disconnect can happen for many reasons, network down, server down, restart etc...  We currently log a WARN message to indicate this has happened.  However, the WARN message includes a stack trace which can look like something has failed or an error has occurred.
> We should remove the stack trace from this WARN message



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