STOMP Tester (over WebSockets)
not connected
Enter the Web-STOMP WebSocket URL — for RabbitMQ the default is wss://your-host:15674/ws.
Add the broker login and passcode (RabbitMQ ships with guest/guest, valid only from localhost), and a vhost if you use one.
Click Connect — the feed confirms the broker software and protocol version that answered.
Subscribe to a destination like /topic/events or /queue/orders; incoming messages stream into the feed.
Send a message to any destination and watch it arrive on your own subscription for an instant loopback test.
STOMP is the text protocol that message brokers speak to the web: RabbitMQ’s Web-STOMP plugin, ActiveMQ and Artemis all expose it over WebSockets precisely so browsers can join the party. This tester is a full STOMP client in a page — connect with your broker login, subscribe to /queue/… and /topic/… destinations, send messages, and watch what flows.
It is the fastest way to answer the everyday broker questions: are messages actually arriving on this queue, is the routing key doing what the diagram claims, do these credentials have permission to publish here? The CONNECTED frame even reports the broker software and STOMP version, so you know exactly what answered.
100% private“The STOMP session runs directly between your browser and the broker over the encrypted WebSocket — credentials, destinations and message bodies never touch this site, because it has no server to touch.”
Enable the rabbitmq_web_stomp plugin and the listener appears on port 15674 at path /ws — behind TLS that becomes wss://host:15674/ws (or whatever your reverse proxy exposes). ActiveMQ and Artemis expose STOMP-over-WebSocket on their own ports; check the broker’s transport connector config.
By design: RabbitMQ’s default guest account only works from localhost. Create a real user with permissions on the vhost you are testing, or you will get an authentication failure no matter how correct the password is.
No — AMQP is a different binary protocol on port 5672, which browsers cannot reach. STOMP over WebSockets is the browser-friendly door into the same brokers, which is exactly why RabbitMQ ships the Web-STOMP plugin.