Hi Ed, You mentioned that using a unique subscription ID does not resolve this issue. Can you confirm that using different subscription IDs across all your clients is the same? Were you seeing subscription semantics before the error (i.e. was every subscription seeing every message?).
I've taken a quick look and there may be an issue in the STOMP protocol handler. The subscription ID is used to identify consumer queues, this could cause some issues with multiple clients using the same subscription ID during unsubscribe. The subscription ID only needs to be unique within connections https://stomp.github.io/stomp-specification-1.2.html#SUBSCRIBE Thanks Martyn
