On 07/09/16 16:00, Flores, Paul A. wrote:
Circumstance:
A process creates a queue with a unique address to mimic synchronous processing
configuring the queue so it is deleted the instance the Receiver is closed, creates a
Receiver for the specific queue, sends a message with the unique "reply to "
address onto another queue and performs a Get with a long time out duration. The process
aborts or the system hosting the process experiences a catastrophic event.
Questions:
Can the broker "tell" that the Receiver process has aborted?
Yes
What is the disposition of the queue with the unique address in this
circumstance?
With the Receiver "disappearing" is the queue "removed" from the broker?
It depends on what you mean by 'configuring the queue so it is deleted
the instance the Receiver is closed'. A temporary queue will indeed
generally be deleted as soon as the owning session ends (whether cleanly
exiting or through a crash)
If the queue is removed:
What happens to Senders attached to the queue?
Depends which protocol you are using. On AMQP 1.0 the senders should be
detached with an error. On AMQP 0-10 they will not.
If the queue remains:
Can another Receiver be attached to the queue to fetch messages and close the
queue?
Yes.
Will the queue ever get "removed" from the broker?
Is the "process" to remove "orphaned" queues manual or can it be automated?
It depends on the configuration of the queue. There is no cleanup that
would apply to all queues regardless of configuration, since determining
what 'orphaned' means is context specific.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
