Streaming Text Oriented Messaging Protocol

Simple (or Streaming) Text Oriented Message Protocol (STOMP), formerly known as TTMP, is a simple text-based protocol, designed for working with message-oriented middleware (MOM). It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol.¹²

The protocol is broadly similar to HTTP, and works over TCP using the following commands:³

• CONNECT
• SEND
• SUBSCRIBE
• UNSUBSCRIBE
• BEGIN
• COMMIT
• ABORT
• ACK
• NACK
• DISCONNECT

Communication between client and server is through a "frame" consisting of a number of lines. The first line contains the command, followed by headers in the form <key>: <value> (one per line), followed by a blank line and then the body content, ending in a null character. Communication between server and client is through a MESSAGE, RECEIPT or ERROR frame with a similar format of headers and body content.

SEND
destination:/queue/a
content-type:text/plain

hello queue a
^@

Here ^@ is the caret notation for the null character. Lines are ended with LF (\n, ^J, 0x10).

Some message-oriented middleware products support STOMP,⁴ such as:

• Apache ActiveMQ
• Fuse Message Broker⁵
• HornetQ
• Open Message Queue (OpenMQ)
• RabbitMQ⁶
• syslog-ng⁷
• Spring Framework⁸