[ 
https://issues.apache.org/jira/browse/QPID-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676901#comment-13676901
 ] 

Rob Godfrey commented on QPID-4910:
-----------------------------------

It is not currently implemented (in 0.20 or the about to be released 0.22)

It looks like there are two mechanisms that the Java broker would have to 
implement in order to support the automated failover built into the Ruby, C++ 
and Python clients

1) sending a list of knownHosts in the ConnectionOpenOK frame
2) implementing the amq.failover exchange 

Implementing 1) should be a reasonably easy change to the broker - it will 
require adding configuration to the virtual host to identify the alternate 
brokers which a client should try on failover. Implementing 2) may be a little 
more involved as it would be a new exchange with the property that the broker 
itself generates messages.


                
> Python, Ruby, and C++ clients automatically connect to replica server when 
> master fails
> ---------------------------------------------------------------------------------------
>
>                 Key: QPID-4910
>                 URL: https://issues.apache.org/jira/browse/QPID-4910
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.20
>         Environment: C++, Ruby, Python, and Java clients connecting to a Java 
> Broker running on Redhat 6.3
>            Reporter: James Belch
>             Fix For: Future
>
>
> I am currently in the process of designing a high availability solution for 
> our software.  We are using the Java broker, and we have Java, Ruby, C++, and 
> Python clients.  I was reading your High Availability document at 
> http://qpid.apache.org/books/0.18/AMQP-Messaging-Broker-Java-Book/html/High-Availability.html
>  and saw a footnote at the bottom stating "[1] The automatic failover feature 
> is available only for AMQP connections from the Java client. Management 
> connections (JMX) do not current offer this feature."  Is this still the case 
> or was this fixed in .20?  If this is still the case, will it be fixed in a 
> future release?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to