QueueExplorer is a desktop client for inspecting, repairing, and managing messages across Azure Service Bus, RabbitMQ, MSMQ, and ActiveMQ Classic, giving developers and administrators a practical alternative to built-in consoles when diagnosing message flow problems.
QueueExplorer is a desktop application that lets developers and administrators browse, inspect, and repair messages in Azure Service Bus, RabbitMQ, MSMQ, and ActiveMQ Classic from a single interface. Instead of writing throwaway diagnostic code or fighting limited web consoles, you open a queue, watch messages arrive in real time, and act on them directly. The workflow follows the way investigations actually happen: connect to a broker, filter and sort the message list, open individual messages to read bodies and headers, then edit, move, replay, or delete the ones causing trouble. QueueExplorer also manages queueing objects, so schema creation, comparison, and migration sit alongside day-to-day troubleshooting in the same workspace.
Where QueueExplorer differs from broker portals is depth on individual messages. Full bodies are rendered as formatted JSON or XML, text in multiple encodings, hexadecimal, WCF content, or .NET serialized objects, and every header or custom property can become a sortable column. Dead-lettered messages show the broker's own failure details, so you can correct the payload and resubmit it to the original destination or another one. Teams that already keep a network debugging utility such as HTTP Analyzer V7 on hand for HTTP traffic tend to treat QueueExplorer as the equivalent for asynchronous messaging: one window that shows what is really moving between services. Connections, groups, and tabs keep development, staging, and production visible side by side.
The main benefit of QueueExplorer is speed during incidents. A growing queue, a poison message, or a stalled consumer stops being a guessing game: you see the queue depth, open the offending message, fix the payload, and send it back, all without redeploying code. Automatic refresh keeps a live view of the whole broker, so problems surface before support tickets arrive. Because one installation speaks to four messaging systems, teams migrating between MSMQ, RabbitMQ, ActiveMQ Classic, and Azure Service Bus keep the same tool and the same habits rather than relearning a new console. Backup and restore to .mq files, CSV import and export, and the built-in bulk sender make testing reproducible: capture real messages from production, replay them in a safe environment, and generate load on purpose. Read-only mode lets cautious administrators investigate production without exposing destructive commands.
Messages start appearing the moment a queue opens, so an investigation can begin before the requested batch finishes loading. View limits of 10, 100, 1,000, 10,000, or show-all keep large production queues manageable, while queue and message views refresh automatically to reflect what producers and consumers are doing right now.
Select any row to inspect its body and properties immediately. QueueExplorer renders formatted JSON and XML, text in several encodings, hexadecimal data, WCF content, and .NET serialized objects where the broker supports them, removing the need to decode payloads by hand before deciding what a message contains.
Damaged payloads can be corrected and sent back to the original queue or a different destination. QueueExplorer performs a new broker send rather than an in-place update, so broker-assigned identifiers, timestamps, and delivery state may change. Requeuing dead-lettered and journaled messages is supported wherever the broker exposes it, which shortens recovery during incidents.
Dead-lettered messages keep the broker's own reason for the failure, along with the original destination where that is recorded, so diagnosis starts from facts instead of guesses. QueueExplorer lets you repair and replay those messages, purge them, export them as incident evidence, or save them for a later test run against a patched consumer.
Save selected messages to compressed .mq files and load them later into a compatible queue. Body bytes can be exported for other tools, messages can be created from body files, selected fields move to CSV, and messages import from CSV. This suits incident evidence, migration, and repeatable tests rather than full broker backup.
Create, inspect, edit, purge, or delete supported queues and related objects, including topics, subscriptions, exchanges, bindings, policies, shovels, and sessions. Copying, comparing, and synchronizing schema between servers helps teams propagate configuration from development to staging or production without repetitive manual console work.
Compose test messages by hand or from a file, choose an encoding, set the editable properties, and send them to a queue or topic to exercise a consumer without waiting for a real producer. QueueExplorer's bulk sender creates hundreds or thousands of copies with an adjustable delay between sends for load and scalability testing.
Run in a restricted read-only mode so production investigations never expose message or queue mutation commands, with broker permissions still limiting access independently. Dark and light themes, HiDPI-friendly vector icons, adjustable text size, and automatic grouping of queue names that share a common prefix keep large environments readable.
One installation works with Azure Service Bus, RabbitMQ, MSMQ, and ActiveMQ Classic. Each broker keeps its own limits, so the operations available for dead-letter handling, sessions, streams, or schema objects depend on what that messaging system supports. Working across several systems from the same interface means teams do not need a separate tool per broker.
Yes. Open the message, correct the supported body or application fields, and send it to the original queue or another destination. The repair is a fresh broker send rather than an in-place update, so broker-assigned IDs, timestamps, and delivery position can change. Dead-lettered and journaled messages can be requeued where the broker exposes that operation.
It complements them. QueueExplorer goes deeper on individual messages than most web consoles: progressive browsing with configurable limits, full body and header viewing, multi-field filters, drag-and-drop between queues, and bulk operations on many selected messages at once. Administrators still use native portals for account and namespace administration.
Read-only mode disables message and queue mutation commands for the session, which lets an investigation look at live traffic without risking accidental changes. This is a client-side safeguard only, so broker permissions should be restricted separately to ensure the credentials used cannot perform destructive operations.
Professional adds schema and metadata operations for exporting, importing, comparing, copying, and synchronizing queue definitions between servers. It also adds custom columns that extract values from JSON, XML, text, or .NET payloads using JSON expressions, XPath, or regular expressions, plus saved Queue Views and custom folders for organizing large environments.
Yes. The bulk sender creates hundreds or thousands of message copies with an adjustable delay between sends, which is useful for checking how a consumer behaves under sustained load. Saved .mq files and CSV imports let you replay a realistic message mix instead of synthetic payloads. Run such tests in an isolated environment and watch quotas.
Comments