Show TOC

Procedure documentationMonitoring JMS Provider Using Telnet Locate this document in the navigation structure

 

Using Telnet commands you can access the following runtime information of the JMS Provider:

  • are there any messages that are sent but not acknowledged yet

  • when was the last message for a particular destination delivered to a consumer

  • does a particular destination have dead (undeliverable) messages

  • browse the messages in a particular Queue

  • what is the configuration and current status of a JMS Store-and-Forward Agent for a particular application

Currently, all these monitors are available via the jms_monitor Telnet command in the jms group.

Procedure

Monitoring the JMS Provider using the jms_monitor command

The common syntax of the command is jms_monitor <commandOption> [vp=<virtualProviderName>] <additionalParameter>, where the name of the JMS Virtual Provider [vp=<virtualProviderName>] is optional and the additional parameter is the name of a destination or the name of an application.

Telnet Command

Description

Example

jms_monitor -p [vp=<virtualProviderName>] [dest=<destinationName>]

or

jms_monitor -pending [vp=<virtualProviderName>] [dest=<destinationName>]

Pending messages are such messages, which are sent but not acknowledged yet. This monitor lists all pending messages for a given destination.

jms_monitor -p vp=default dest=sapDemoTopic

If you specify only the name of a Virtual Provider, you get all pending messages for all destinations that belong to that particular Virtual Provider.

jms_monitor -p vp=default

If you do not specify any Virtual Provider or destination, you get all pending messages for all destinations and their corresponding Virtual Providers.

jms_monitor -p

jms_monitor -lastDeliveryTime [vp=<virtualProviderName>] <dest=destinationName>

Displays the last time the message was delivered to a consumer registered to the specified destination.

jms_monitor -lastDeliveryTime vp=default dest=sapDemoQueue

jms_monitor -deadMsgAlert[vp=<virtualProviderName>] <dest=destinationName>

Shows if there are any dead messages for the specified destination. If there are dead messages, the deadMessagesAlert flag is set to true.

jms_monitor -deadMsgAlert vp=default dest=sapDemoQueue

jms_monitor -resetDead[vp=<virtualProviderName>] <dest=destinationName>

This command resets the deadMessagesAlert flag.

jms_monitor -resetDead vp=default sapDemoQueue

jms_monitor -browseQueue [vp=<virtualProviderName>] <dest=destinationName>

Creates a QueueBrowser to view the messages of the specified Queue.

Note Note

This monitor is available only for queues.

End of the note.

jms_monitor -browseQueue vp=default dest=sapDemoQueue

jms_monitor -safAgentStatus [vp=<virtualProviderName>] <app=applicationName>

Shows the status of the Store-and-Forward (SAF) Agent of the specified application and general information about its local and remote resources. The status of the SAF Agent can be: RUNNING, STOPPED, NOT_AVAILABLE.

jms_monitor -safAgentStatus vp=default app=sap.com/mySAFApplication

jms_monitor -cacheSize [vp=<virtualProviderName>]

Shows the size of the currently used server-side message cache in bytes.

jms_monitor -cacheSize vp=default

jms_monitor -cacheCount [vp=<virtualProviderName>]

Shows the number of messages currently cached on the server.

jms_monitor -cacheCount vp=default