...
Each of the MessageStore implementations provide different back end storage for their messagess messages and so would need a different tool to be able to interrogate their contents. What this tool does is to utilise the Java broker code base to access the contents of the storage providing the user with a consistent means to inspect the storage contents. The tool allows the current messages in the store to be inspected and copied/moved between queues.
...
On startup the user is present with a command prompt
No Format |
---|
$ msTool.sh MessageStoreTool - for examining Persistent Qpid Broker MessageStore instances bdb$ |
Available Commands
The available commands in the tool can be seen through the use of the 'help' command.
No Format |
---|
bdb$ help +----------------------------------------------------------------+ | Available Commands | +----------------------------------------------------------------+ | Command | Description | +----------------------------------------------------------------+ | quit | Quit the tool. | | list | list availbleavailable items. | | dump | Dump selected message content. Default: show=content | | load | Loads specified broker configuration file. | | clear | Clears any selection. | | show | Shows the messages headers. | | select | Perform a selection | | help | Provides detailed help on commands. | +----------------------------------------------------------------+ bdb$ |
Available Commands
The availale commands in the tool can be seen through the use of the 'help' command.
A brief description is displayed and further usage information is shown with 'help <command>'
No Format |
---|
bdb$ help dump
Dump selected message content. Default: show=content
Usage:dump [show=[all],[msgheaders],[amqHeaders],[routing],[content]] [id=<msgid e.g. 1,2,4-10>]
bdb$
|
Future Work
Currently the tool only works whilst the broker is offline. If this functionality was incorporated into the broker then a telnet functionality could be provided allowing online management.