[
https://issues.apache.org/jira/browse/AMQ-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585913#comment-16585913
]
Christopher L. Shannon edited comment on AMQ-7036 at 8/20/18 1:15 PM:
----------------------------------------------------------------------
Yeah this was my concern on this. The problem with logging is different people
want to see different things by default so it's hard to make everyone happy.
The patch or part of it may need to be reverted as it is probably too verbose
if existing users are complaining about the behavior changing. I will take a
look but the solution might be to just to rollback the patch and tell people to
enable debug logging for the FailoverTransport if they really want to see more
detail.
was (Author: christopher.l.shannon):
Yeah this was my concern on this. The problem with logging is different people
want to see different things by default so it's hard to make everyone happy.
The patch or part of it may need to be reverted based on AMQ-7036 being too
verbose as if existing users are complaining about the behavior changing that
isn't great. I will take a look but the solution might be to just to rollback
the patch and tell people to enable debug logging for the FailoverTransport if
they really want to see more detail.
> FailoverTransport should not report errors trying to connect to Slave Broker
> ----------------------------------------------------------------------------
>
> Key: AMQ-7036
> URL: https://issues.apache.org/jira/browse/AMQ-7036
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.15.5
> Reporter: Martin Lichtin
> Priority: Major
>
> Going from 5.15.4 to 5.15.5 the failover transport is now constantly spitting
> out error messages. This wasn't the case with 5.15.4.
> {noformat}
> 2018-08-17 12:55:13,422 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:13,431 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:13,942 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:14,947 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:15,952 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:16,412 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:16,414 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:16,425 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:21,968 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:28,425 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:35,998 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:37,003 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:37,412 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:37,422 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:38,009 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:39,014 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:40,019 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:40,414 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> 2018-08-17 12:55:40,456 | ERROR | ActiveMQ Task-1 |
> FailoverTransport | sport.failover.FailoverTransport 1060 |
> 130 - org.apache.activemq.activemq-osgi - 5.15.5 | Connect fail to:
> nio://172.22.55.4:11000?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false,
> error message: Connection refused
> {noformat}
> The FailoverTransport obviously cannot connect to the Slave Broker. It should
> not report this as an error.
> Additional (but unwanted) error log was added by AMQ-7004
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
