Description
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.
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
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
Attachments
Issue Links
- is caused by
-
AMQ-7004 Request for improved FailoverTransport logging
- Resolved