@petegehrman yes, this is a super useful pattern in Solace, essentially a network mutex. We use this heavily in various production scenarios where you want to ensure only one active participant… e.g. HA publishers: have multiple publishers available to publish some stream of data onto Solace, but only the guy who has the ACTIVE_FLOW_NOTIFICATION from their shared exclusive queue is the live publisher. (they’re only using the queue to determine who’s active, not subscribing to anything).
Just did some Googling, and I’m surprised that I don’t see a Solace blog about this well-known pattern. Huh! Maybe one of us should go write one…! ?