You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2018/09/04 10:53:00 UTC
[jira] [Commented] (AMQ-7036) FailoverTransport should not report
errors trying to connect to Slave Broker
[ https://issues.apache.org/jira/browse/AMQ-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602894#comment-16602894 ]
Christopher L. Shannon commented on AMQ-7036:
---------------------------------------------
I'm going to cut 5.15.6 today so for now I am just going to rollback the previous patch as it is a regression for some people. If desired we can create another Jira for a future release, such as 5.15.7 or 5.16.0, that can incorporate Tim's suggestion or some otherway to increase the logging.
> 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)