On 02/08/2011 06:01 PM, Kerry Bonin wrote:
I'm interested in the classic durable subscription case - two clients and a broker, client 2 has a durable subscription to a queue, client 1 sends something to that queue while client 2 is disconnected. When client 2 reconnects it would like to receive the messages it missed. Ideally this could include a power cycle of the broker, hence my interest in the database persistence module.
For a queue, providing the messages and queue are durable, and the transfer to the consumer is reliable i.e. acknowledged (which it is by default for queues), you shouldn't need to do anything further.
I've enabled the mssql persistence module, but the next steps are unclear - I've found conflicting information on how to setup the subscription, and am hoping to avoid stepping into the broker to figure out what I'm missing or doing wrong.
What are the symptoms you are seeing? Just not having messages recovered? Are the messages durable?
We're using the C++ broker and have been building from recent sources. I'm also curious if there is support / plans for durability on the client side - having the client queue sent messages if the broker is temporarily offline.
Nothing planned as such (i.e. definite intention to implement expressed) that I'm aware of, though you are not the first person to mention it.
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
