Protocols
Saved & recent

STOMP

Also called: Simple Text Oriented Messaging Protocol, STOMP 1.2

STOMP is a simple protocol for exchanging messages through a server. STOMP 1.2 frames have a command, headers and an optional body, which may contain binary data. Clients use commands such as SEND and SUBSCRIBE; servers deliver MESSAGE frames. Destination strings are intentionally opaque, so their queue or topic behavior depends on the server.

For example, a worker subscribes to a broker’s /queue/labels destination using ack:client-individual. After handling a MESSAGE, it sends the corresponding ACK. That path is a broker convention, not a universal STOMP naming rule. Choosing auto acknowledgment changes the guarantee: the server assumes delivery when it sends the message, rather than waiting for an explicit client acknowledgment.

Read first
Message broker
Related
Message broker, Consumer acknowledgment, WebSocket
Further reading
STOMP — Protocol specification 1.2
worker broker subscribe SUBSCRIBE id:labels destination:/queue/labels ack:client-individual delivery MESSAGE subscription:labels message-id:7 ack:m7 after processing ACK id:m7 STOMP 1.2 · broker-specific destination
STOMP 1.2 client-individual mode: after processing MESSAGE ack:m7, the worker sends ACK id:m7. These are frame excerpts; /queue/labels is a broker-specific destination convention.

View in the full Protocols collection