[
https://issues.apache.org/jira/browse/ARTEMIS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989660#comment-14989660
]
ASF GitHub Bot commented on ARTEMIS-296:
----------------------------------------
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/233
ARTEMIS-296 Remove stacktrace from bridge disconnect log
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-296
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/233.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #233
----
commit d40d2e5705acfaea4df6402ce7d4000552e7cbbd
Author: Martyn Taylor <[email protected]>
Date: 2015-11-04T15:04:12Z
ARTEMIS-296 Remove stacktrace from bridge disconnect log
----
> 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
>
> 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)
