[
https://issues.apache.org/jira/browse/AMQ-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102655#comment-15102655
]
ASF subversion and git services commented on AMQ-5336:
------------------------------------------------------
Commit 4ea435bf460e68a3f1fc2addadc9b683742cc40d in activemq's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4ea435b ]
https://issues.apache.org/jira/browse/AMQ-5336
URI comparison needs to be done using the host / port comparison method
instead of string equality due to other features like nested options
which can alter the URIs and lead to continued attempts to reconnect to
the transport that's already connected when priority backup is used.
> Validate priorityBackupURIs against list of failover URIs
> ---------------------------------------------------------
>
> Key: AMQ-5336
> URL: https://issues.apache.org/jira/browse/AMQ-5336
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.10.0
> Reporter: Lee Butts
> Fix For: 5.14.0
>
>
> The following priority back up config does not work:
> {code}
> failover:(tcp://localhost:1234,tcp://primary1:1234,tcp://secondary1:1234)?
> nested.socket.tcpNoDelay=true&
> nested.soTimeout=60000&
> nested.closeAsync=false&
> randomize=false&
> priorityBackup=true&
> priorityURIs=tcp://localhost:1234
> {code}
> This is because the full connected URI is used when testing whether the
> current connection is the priority connection. In the above example the
> nested socket params are added to the actual connected URI which then does
> not match tcp://localhost:1234 as setup in the priority list.
> This causes the transport to continually try to reconnect to the primary,
> even though it is already connected to it.
> Can it either take nested parameters into account so the above works as
> expected (it looks like a sensible URL to me) and/or validate that each of
> the priorityBackupURIs are valid URIs in the failover list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
