Asynch examples on ActiveMQ - Artemis about stompest HOT 1 CLOSED

The Artemis frame contains two Stomp protocol headers I wouldn't expect. First, it loops through the receipt header. This shouldn't be a problem, though. Second, the subscription header is added although no id header was given (which is optional in Stomp 1.0). The protocol specification says:

You can also specify an id header which can then later on be used to UNSUBSCRIBE from the specific subscription as you may end up with overlapping subscriptions using selectors with the same destination. If an id header is supplied then Stomp brokers should append a subscription header to any MESSAGE commands which are sent to the client so that the client knows which subscription the message relates to.

To sum up, you can/should do either of the following:

1. File a bug to Artemis because their implementation of STOMP 1.0 isn't correct and wait until it's fixed.
2. Add an explicit id(properly coded, that would be StompSpec.ID_HEADER) header to work around the Artemis bug.

Probably you shouldn't use Stomp 1.0 in the first place because it's an under-specified protocol (no NACK frames, no header escaping, no heartbeating). Actually, I recommend to start new projects on Stomp 1.2 or (if your broker doesn't support it) Stomp 1.1.

from stompest.