JMS
This section describes the commands for the JMS Provider service. They are added to the shell environment by executing ADD JMS on the command line.
LIST
Syntax |
LIST [options] [instanceName] |
Arguments |
|
[options] |
The following options are available: · destinations – displays the instance destinations. If no instance name is specified, it shows all the available JMS destinations. · connections – displays the instance connection. If no instance name is specified, it shows all the available JMS connections. · sessions – displays the instance sessions. If no instance name is specified, it shows all the available JMS sessions. · producers – displays the instance producers. If no instance name is specified, it shows all the available JMS producers. · consumers – displays the instance consumers. If no instance name is specified, it shows all the available JMS consumers. · browsers – displays the instance browsers. If no instance name is specified, it shows all the available JMS browsers. · configurations – displays the instance configurations. If no instance name is specified, it shows all the available JMS configurations. · subscriptions – displays the instance durable subscriptions |
[instanceName] |
The name of the instance to display the data available for. |
Description |
Lists all the specific commands for the default instance. If no instance name is specified the data for the “default” instance is displayed. |
JMS LIST DEADMSGS
Syntax |
JMS LIST DEADMSGS [<instanceName>] |
Arguments |
|
[<instanceName>] |
JMS server instance name |
Description |
Displays a list of destinations (defined within the specified JMS server instance) that contain dead messages as well as the number of dead messages. If no instance name is given, the information is shown for all JMS server instances. |
JMS EXPORT
Syntax |
JMS EXPORT -d -f <fileName> -i [instanceName] |
Arguments |
|
<fileName> |
The XML file name |
[instanceName>] |
JMS server instance name |
Description |
Exports the dead messages of all queues defined within the specified JMS server instance to an XML file. The name and path of the file has to be provided as a parameter. If no instance name is given, the dead messages of all JMS server instances are exported. For example, you can use this file to fix corrupt message data. |
JMS IMPORT
Syntax |
JMS IMPORT -f <fileName> |
Arguments |
|
<fileName>] |
The XML file name |
Description |
Imports the JMS messages that are contained in the specified XML file. The file must be given with its full path. The messages are appended to the queue given in the JMSDestination header field, just as if they were sent at that time. The existing message header fields, however, remain unchanged. After being imported successfully, the dead message is removed from the error queue.
Multiple dead messages in the file are imported sequentially in the order they appear in the file. The operation is not transactional: In case an error occurs while processing message (n+1), the first n messages have already been imported. This must be taken into account in case that the import is attempted again. You has to remove the imported messages manually from the XML file to avoid duplicates, or alternatively, start with a new export again. |
