[AMQ-7004] Request for improved FailoverTransport logging

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 5.15.5, 5.16.0
• Assignee: Christopher L. Shannon
• Reporter: Andy Brown
• Created: 29/Jun/18 09:00
• Updated: 04/Sep/18 10:55
• Resolved: 30/Jul/18 11:58

Description

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.

Issue Links

• causes: AMQ-7036 FailoverTransport should not report errors trying to connect to Slave Broker