activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-296) Do not print stack trace on BridgeDisconnect
Date Fri, 20 Nov 2015 22:54:11 GMT


Justin Bertram commented on ARTEMIS-296:

This looks resolved to me.  Can you confirm, [~martyntaylor]]?

> Do not print stack trace on BridgeDisconnect
> --------------------------------------------
>                 Key: ARTEMIS-296
>                 URL:
>             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

View raw message