[
https://issues.apache.org/jira/browse/AMQ-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon resolved AMQ-7004.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.15.5
5.16.0
[~foxbat] - See what you think about the changes..I kept the original debug
message with the full stack trace but added a new error message that contains
the URI and just the message to prevent filling up the log with stack traces.
This is the same pattern the rest of the broker generally uses (just log the
message under warn/error and only log the full stack trace under debug)
> Request for improved FailoverTransport logging
> ----------------------------------------------
>
> Key: AMQ-7004
> URL: https://issues.apache.org/jira/browse/AMQ-7004
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Andy Brown
> Assignee: Christopher L. Shannon
> Priority: Trivial
> Fix For: 5.16.0, 5.15.5
>
>
> This is a request for improved logging based on a recent production outage
> that could have been identified and resolved much faster with better logging
> in the FailoverTransport.
> Cluster update notifications are not logged. These are important, hopefully
> infrequent events and should be logged at INFO level in the updateURIs method:
> [https://github.com/apache/activemq/blob/master/activemq-client/src/main/java/org/apache/activemq/transport/failover/FailoverTransport.java#L1279]
> The exception that gives the cause of the failure to failover is logged at
> DEBUG level. This hid the root cause of the problem from us until we managed
> to figure out that additional information was available but hidden, and we
> turned up the logging level of the running client to DEBUG. Please turn this
> log line up to ERROR:
> [https://github.com/apache/activemq/blob/master/activemq-client/src/main/java/org/apache/activemq/transport/failover/FailoverTransport.java#L1279]
> Hopefully these are really trivial changes that you can make that will
> definitely enhance the operational transparency of the running clients.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
