activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Reopened] (AMQ-5336) Validate priorityBackupURIs against list of failover URIs
Date Fri, 15 Jan 2016 19:20:39 GMT


Timothy Bish reopened AMQ-5336:

resolved the wrong issue. 

> Validate priorityBackupURIs against list of failover URIs
> ---------------------------------------------------------
>                 Key: AMQ-5336
>                 URL:
>             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
> 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

View raw message