On 09/10/2013 03:15 PM, Darryl L. Pierce wrote:
On Mon, Sep 09, 2013 at 05:25:47PM -0600, Rajesh Khan wrote:
Is there anyway for qpid to know that the sender has disconnected even if
the sender does not elegantly disconnect by code ?
I think, based on what Gordon said in another email, there's no easy way
to detect this; i.e., I think he said the queue stays in place in that
scenario.
The way the 'delete: always' (or 'delete: sender' for that matter) is
implemented is as an action taken by the _client_ when closing the link.
Therefore if the client process exits without doing this, the action
isn't performed.
The auto-delete property for queues is implemented on the broker side.
However in this case the node is (as I understood it) supposed to be an
exchange. We don't implement auto-delete for exchanges, and in any case
the way it is defined to work (by the 0-10 specification) is to trigger
delete when there are no bindings.
Perhaps, like a heart beat, if the client doesn't receive two messages
within a set period of time, it can treat that situation as if the
sender has disconnected?
The issue is not detecting that the sender has disconnected. It is in
specifying that this should trigger deletion of the node.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
