Hi Gordon , Thanks for the reply this might solve the problem however I read from the manual that with "delete:always" if the receiver disconnects from the topic the topic will also be deleted. I do not want that behavior. What I am looking for is if the Sender shuts down the topic should be deleted And the listeners should get an exception.
On Mon, Sep 9, 2013 at 1:35 PM, Darryl L. Pierce <[email protected]> wrote: > On Mon, Sep 09, 2013 at 01:15:26PM -0400, Rajesh Khan wrote: > > Currently I have an app call it "Sender" that creates topics using the > > following string > > > > std::string sender_string = queue_name +";{create:always, delete:always, > > node:{type:topic}}"; > > > > Now I was under the impression that if the sender application closes for > > some reason The Broker would delete the topics created by the sender and > > all those applications that were listening to the topic would get an > > exception however this is not happening. Am I missing something here ? > Any > > suggestions ? > > I just used the spout example app on a fresh Qpid broker (no existing > messages, exchanges or queues): > > $ ./spout "my-queue;{create:always, delete:always, node:{type:topic}}" > > and afterward found no queue. > > What is the name of your queue? And was the queue by any chance already > there when your client connected to the broker? > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > Red Hat ranks #1 in value among software vendors. > http://www.redhat.com/promo/vendor/ > >
