[
https://issues.apache.org/jira/browse/AMQ-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244080#comment-17244080
]
Matt Pavlovich commented on AMQ-6399:
-------------------------------------
This issue is most likely addressed with a more recent build of ActiveMQ, and
specifically using the masterslave: uri in a networkConnector configuration.
This issue is being marked close-pending and will be closed in 30 days if there
is no response. This issue is most likely resolved in more recent releases than
5.0.0.
Please test with a 5.15.14 or 5.16.0 release and report back if this is still
an issue.
> 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
> Priority: Major
>
> 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
(v8.3.4#803005)
