You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Tim Bain (JIRA)" <ji...@apache.org> on 2016/08/18 04:01:20 UTC
[jira] [Created] (AMQ-6399) Log a warning when starting a
networkConnector with static:failover without using maxReconnectAttempts=0
Tim Bain created AMQ-6399:
-----------------------------
Summary: Log a warning when starting a networkConnector with static:failover without using maxReconnectAttempts=0
Key: AMQ-6399
URL: https://issues.apache.org/jira/browse/AMQ-6399
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.0.0
Reporter: Tim Bain
When configuring a networkConnector using the static:failover: transport, you'll be unable to failover if you don't specify the maxReconnectAttempts=0 option on the failover transport.
We periodically see users on the mailing list getting tripped up by this, since it's not intuitive or obvious. One option would be to simply refuse to start the broker when this happens (since there probably isn't a valid reason to configure a networkConnector that way), but since that's probably too draconian, we should instead log a warning that tells the user that this is probably not what they want so they can fix it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)