[
https://issues.apache.org/jira/browse/QPID-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677068#comment-13677068
]
Gordon Sim commented on QPID-4910:
----------------------------------
Note that you can manually configure the clients with a list of brokers to try
and then on failover they go through that list (this is similar to the use of a
round-robin failover policy in the jms clients connection 'url'). I.e. the
mechanisms above are used to inform the clients of the location of backups, but
are not strictly needed for the actual failover and replay logic.
> 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: 0.23
>
>
> 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]
