If Queue state replication is not impacted by QPID-2199, that would be a solution. However 2199 seems to be a link issue, which would mean it would. On 05/05/2010 02:04 PM, Kerry Bonin wrote:
I've been walking down a rat hole and thought I'd take a moment to ask the list how I should proceed - I could use some advice from someone with deeper QPID experience... My requirement is relatively simple - I've got a number of clients using QPID , all currently Windows platforms, with clients in C++, Python, and Java. We need the system to handle broker process / host failure, preferably in a manner transparent to the client applications (although we can insert code between the client applications and the QPID client library.) We can run multiple brokers, and had planned on deploying a broker on each server box, and wanted at least some sort of failover solution. Our problem - how to proceed on Windows? QPID Clustering is built over Corosync, which I believe limits it to a subset of *nix platforms. Federation with failover would work, but Federation doesn't work on Windows. (I'm still looking at QPID-2199...) Failover code in progress appears tied to clustering, which is out for Windows. Should I just roll my own standalone failover, forking if necessary to expose lower features? (I don't want to do this!) Can I leverage the Failover code in the trunk and manage amq.failover without the Corosync dependent code? Are there any simpler approaches I'm missing? Comments greatly appreciated... --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
