STOMP

STOMP is the text messaging protocol used notably by Spring applications (spring-websocket) and ActiveMQ. Restorm implements it over WebSocket.

Right-click in the tree ▸ Add ▸ STOMP request.

Configuration

Field	Role
URL	ws:// or wss://
STOMP version	1.1 or 1.2
Connection headers	The CONNECT frame’s headers: host, login, passcode, heart-beat…
Subscriptions	A list: identifier, destination, acknowledgement mode
Send destination	The SEND frame’s destination
Send body	The SEND frame’s payload
Send headers	The SEND frame’s headers

Subscriptions

Each subscription carries an acknowledgement mode:

Mode	Behaviour
auto	The broker considers the message delivered as soon as it is sent
client	Cumulative acknowledgement by the client
client-individual	Acknowledgement message by message

On connecting, Restorm emits the CONNECT then one SUBSCRIBE per configured subscription.

Credentials

STOMP has no dedicated credential fields: login and passcode are ordinary connection headers. Use a Secret-typed value for the passcode.

In a scenario

STOMP connect (emits the CONNECT and the SUBSCRIBE frames, connected and message outputs), STOMP send (SEND frame) and STOMP close (DISCONNECT). See Connections and streams.

TLS

On a wss:// URL, server certificate verification is currently disabled. That is convenient against a development broker with a self-signed certificate, but keep it in mind if you are aiming at a production gateway.

Code snippets

Two targets: Node.js (@stomp/stompjs) and wscat.