Making queue writable only if there is at least one consumer

I'm building a queuing solution involving multiple data centers. Requests that come into one center should be processed there - if that center isn't able to process them, it is preferable to have the requests rejected at the entry point so that remote clients can failover to one of the other

0.24 release update - Release branch created, beta is available

Hi, folks. Yesterday at revision 1504342, we branched for the upcoming 0.24 release. Check it out at this URL: https://svn.apache.org/repos/asf/qpid/branches/0.24/ The beta distribution is from revision 1504344 of the release branch: http://people.apache.org/~jross/qpid-0.24-beta/

RE: Making queue writable only if there is at least one consumer

You can sort of do #2 by auto-deleting the queue when the last consumer disconnects. To avoid orphaning any messages, you can set up an alternate exchange for the queue, so when the queue is deleted, any messages get rerouted to the alternate exchange. You can use other queues/bindings to