Robert Godfrey wrote:
the issues with no-local and "connections" occur when sessions become disconnected. i.e. what happens does the "owning" connection for the queue change when the session is disconnected from one session and moves to another?
Yes, the currently attached connection for the session is checked when testing the message. If the session that 'owns' the queue is not currently 'attached' then no messages are dropped (the assumption being they can't be on the same connection as that session, since that session has no connection).
If session A and session B start on the same connection and are then resumed on separate connections then the relationship between them is lost. After resuming, if B publishes a message to an exclusive, no-local queue owned by A it will be enqueued (whereas while they were on the same connection it would have been dropped).
