qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajesh Khan <rajeshkhan...@gmail.com>
Subject Re: Any way for topics to be deleted when the creator shuts down
Date Mon, 09 Sep 2013 18:53:20 GMT
While going through the manual I came across the following

Create, Delete, and Assert Policies
The create, delete, and assert policies specify who should perfom the
associated action:

• always: the action is performed by any messaging client
• sender: the action is only performed by a sender
• receiver: the action is only performed by a receiver
• never: the action is never performed (this is the default)

So I am thinking that If I create the sender as such

std::string sender_string = std::string("amq.topic/") + queue_name
+";{create:always, delete:sender, node:{type:topic}}";

The following characteristics would be exhibited (Please correct me if I am

1-Once the sender application stops due to whatever reason the exchange
gets removed and all the receivers would get an exception ?

On Mon, Sep 9, 2013 at 2:23 PM, Rajesh Khan <rajeshkhan808@gmail.com> wrote:

> Any suggestion then on how Qpid could find out if a certain sender
> disconnected. What I want to do is alert the listeners that the sender
> application they were listening to has been disconnected. Also I do not
> want the topic to be deleted once a connected client disconnects. Looks
> Like Ill have to remove "delete:always" from the sender as deleting of
> topics by the listeners is totally unacceptable in my case
> On Mon, Sep 9, 2013 at 2:16 PM, Darryl L. Pierce <dpierce@redhat.com>wrote:
>> On Mon, Sep 09, 2013 at 02:08:59PM -0400, Rajesh Khan wrote:
>> > 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.
>> That seems to be the case. As my (this is Darryl) test showed previously,
>> I sent a message into a queue that was created with
>> "create:always,delete:always". After the spout utility disconnected, and
>> even though there was a message in the queue, it was still deleted.
>> --
>> 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/

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message