[
https://issues.apache.org/jira/browse/AMQ-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586033#comment-16586033
]
Martin Lichtin commented on AMQ-7036:
-------------------------------------
I agree, something special may be required to help Andy's use case.
Looking at where LOG.error is used, it's for cases where the FailoverTransport
cannot do its job. Not being able to connect is quite normal and not an issue
until a reconnect limit is reached. It seems AMQ-7004 asking for a specific
error log is primarily to help, via a log scanner, find network connectivity
problems.
> 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)
