Messaging dashlet

The Messaging dashlet aggregates JMS, MSMQ, Tibco, and other messages by destination and message type. The destination is the name of the queue or topic that a message has been sent to or received from.

Messaging dashlet
Messaging dashlet

Metrics

The following metrics are listed in the Messaging dashlet:

  • Error State: The first, unlabeled column displays icons that indicate the error state of the underlying PurePath (Successful, Failed Transaction, Error).
  • Platform: The second, unlabeled column displays icons that indicate whether the message was transmitted on a Java or .NET platform.
  • QueueManager: The name of the Queue Manager. Available only for WebSphere MQ and MQ Series.
  • Destination and MessageType: The destination and message type of the sent or received message. Each row shows messages grouped by destination and message type.
  • Count Sent: The number of times a message with the particular message type has been sent to this particular destination.
  • Sent Failed %: The percentage of failures detected when sending a message from this destination with this message type.
  • Sent Avg [ms]: The average time, in milliseconds, spent to send a message from this destination with this message type.
  • Sent Min [ms]: The minimum time, in milliseconds, spent to send a message from this destination with this message type.
  • Sent Max [ms]: The maximum time, in milliseconds, spent to send a message from this destination with this message type.
  • Sent Sum [ms]: The accumulated time, in milliseconds, spent to send all messages from this destination with this message type.
  • Sent Avg [bytes]: The average number of bytes required to send a message from this destination with this message type.
  • Sent Min [bytes]: The minimum number of bytes used to send a message from this destination with this message type.
  • Sent Max [bytes]: The maximum number of bytes used to send a message from this destination with this message type.
  • Sent Sum [bytes]: The accumulated number of bytes used to send messages from this destination with this message type.
  • Count Rcvd: The number of times this destination has received a message with this message type.
  • Rcvd Failed %: The percentage of failures detected when this destination has received a message with this message type.
  • Rcvd Avg [ms]: The average time, in milliseconds, spent to receive messages with this message type by this destination.
  • Rcvd Min [ms]: The minimum time, in milliseconds, spent to receive a message with this message type by this destination.
  • Rcvd Max [ms]: The maximum time, in milliseconds, spent to receive a message with this message type by this destination.
  • Rcvd Sum [ms]: The accumulated time, in milliseconds, spent to receive messages with this message type by this destination.
  • Rcvd Avg [bytes]: The average number of bytes used to receive a message with this message type by this destination.
  • Rcvd Min [bytes]: The minimum number of bytes used to receive a message with this message type by this destination.
  • Rcvd Max [bytes]: The maximum number of bytes used to receive a message with this message type by this destination.
  • Rcvd Sum [bytes]: The accumulated number of bytes used to receive messages with this message type by this destination.
  • Count Peeked: The number of times this destination has peeked a message with this message type.
  • Peek Failed %: The percentage of failures detected when peeking at messages with this message type by this destination.
  • Peeked Avg [ms]: The average time, in milliseconds, spent to peek at messages with this message type by this destination.
  • Peeked Min [ms]: The minimum time, in milliseconds, spent to peek at a message with this message type by this destination.
  • Peeked Max [ms]: The maximum time, in milliseconds, spent to peek at a message with this message type by this destination.
  • Peeked Sum [ms]: The accumulated time, in milliseconds, spent to peek at messages with this message type by this destination.
  • Peeked Avg [bytes]: The average number of bytes used to peek at a message with this message type by this destination.
  • Peeked Min [bytes]: The minimum number of bytes used to peek at a message with this message type by this destination.
  • Peeked Max [bytes]: The maximum number of bytes used to peek at a message with this message type by this destination.
  • Peeked Sum [bytes]: The accumulated number of bytes used to peek at messages with this message type by this destination.

Not all of these metrics are available for all message types:

  • Metrics for the size of a sent/received message are not available for JMS message types StreamMessage, MapMessage, and ObjectMessage ; or for Tibco messages.
  • Peeking of messages is only supported by MSMQ. For other message types, such as JMS and Tibco, these columns are empty.

Context menu options

  • Drill Down: Drill down to other analysis dashlets. For example, you can drill down from an entry in the Messaging dashlet to the PurePaths dashlet to view all transactions that have interacted with a certain queue or topic.
  • Create Measures: Open the Measure Configuration dialog box to add measures to a subscription. This option is only available for real-time sessions.
  • New Business Transaction: Open the Business Transaction dialog box to create a new Business Transaction based on measure related to the selection. This option is only available for real-time sessions.
  • Source Lookup See Source Lookup Feature for a detailed description.
  • Add Sensor Rules
    • Refine with Callee Methods: All methods that are called by the selected methods are retrieved and can be used as input for new Inclusion Sensor Rules.
    • Exclude Selected Methods: All selected methods can be used as input for new Exclusion Sensor Rules.
    • Include Selected Methods: All selected methods can be used as input for new Inclusion Sensor Rules.

Sensor Configuration

See Sensor Properties for information on configuring the Messaging Sensors.

Tuning options

Use these guidelines to tune performance:

  • Use getConnection(). JMS connections are served from a connection pool, so calling getConnection() on a queue connection factory is fast.
  • Tune the message-driven EJB´s pool size to optimize the concurrent processing of messages.
  • Cache bean-specific resources. Use the setMesssageDrivenContext() or ejbCreate() method to cache bean-specific resources, and release those resources with the ejbRemove() method.
  • Limit use of JMS connections. When designing an application that uses JMS connections, try to use connections sparingly by either pooling them or using the same connection for multiple sessions. The JMS connection uses two threads and the sessions use one thread each. Because these threads are not taken from a pool and the resultant objects aren't pooled, you could run out of memory during periods of heavy usage. One workaround is to move createTopicConnection into the init of the JSP. Make sure you specifically close the session, because when it stays open it ties up resources.