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.
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. 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. Thanks! On Tue, Feb 8, 2011 at 11:39 AM, Andrew Stitcher <[email protected]>wrote: > On Tue, 2011-02-08 at 11:29 -0600, Kerry Bonin wrote: > > Appreciate any help... > > Could you be a little clearer with what you want? In the current qpid > implementation (in C++ broker at least) durability of messages isn't > related to the transport (which is a networking concept), but to a > persistence plugin. I don't know if this is also true for the Java > broker (if you wanted that) but I'd think it's pretty likely to be true > there too. > > Andrew > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
