Communications counters
These service integration bus communications counters are part of the performance monitoring infrastructure (PMI), which provides server-side monitoring and a client-side API to retrieve performance information. Communications counters are maintained across all components of WAS.
To see available PMI counters
Monitoring and Tuning | Performance Monitoring Infrastructure (PMI) | resource_name | [General Properties] CustomTo navigate to the counters in the admin console.
server_name | SIB Service | SIB Communications | Clients | Standard Statistics
Name Key ID Description Granularity Type Level APIConnectionsCount ClientStats.APIConnections 552 Number of API sessions being used by clients that are currently network connected to this appserver. Some of these API connections might be being by internal system processes on behalf of a client.
current clients/connections connected to this application server CountStatistic Low BufferedReadBytesCount ClientStats.BufferedReadBytes 561 Number of bytes of data that have been received from the network and are held pending further processing. Large values might indicate that the appserver is unable to process data fast enough to keep up with the clients attached.
All clients connected or that have been connected to this appserver CountStatistic Low BufferedWriteBytesCount ClientStats.BufferedWriteBytes 560 Number of bytes of data being held pending transmission. Large values might indicate network congestion or clients that are unable to process data fast enough to keep up with the appserver.
All clients connected or that have been connected to this appserver CountStatistic Low ClientsAttachedCount ClientStats.ClientsAttached 551 Number of distinct client processes currently network connected to this appserver. Current clients/connections connected to this application server CountStatistic Low ErrorsCount ClientStats.Errors 553 Communication errors that have occurred and resulted in a network connection to a client being disconnected. All clients connected or that have been connected to this appserver CountStatistic Low MessageBytesReadCount ClientStats.MessageBytesRead 563 Number of bytes of message data received from client processes over network connections. This does not include data used to negotiate the transmission of messages
All clients connected or that have been connected to this appserver CountStatistic Low MessagesBytesWrittenCount ClientStats.MessageBytesWritten 562 Number of bytes of message data sent to client processes over network connections. This does not include data used to negotiate the transmission of messages
All clients connected or that have been connected to this appserver CountStatistic Low MulticastSendMessageCount ClientStats.MulticastSendMessage 559 Number of messages transmitted using multicast protocols. All clients connected or that have been connected to this appserver CountStatistic Low MulticastWriteBytesCount ClientStats.MulticastWriteBytes 558 Number of bytes transmitted using multicast protocols. All clients connected or that have been connected to this appserver CountStatistic Low ReadsBlockedCount ClientStats.ReadsBlocked 557 Number of read operations that could not be completed immediately. For IBM Service use. All clients connected or that have been connected to this appserver CountStatistic Low ReadsCount ClientStats.Reads 555 Number of read operations used to receive data from client processes via network connections. All clients connected or that have been connected to this appserver CountStatistic Low TotalBytesReadCount ClientStats.TotalBytesRead 565 Number of bytes of data received from client processes. This includes both message data and data used to negotiate the transmission of messages.
All clients connected or that have been connected to this appserver CountStatistic Low TotalBytesWrittenCount ClientStats.TotalBytesWritten 564 Number of bytes of data sent to client processes. This includes both message data and data used to negotiate the transmission of messages.
All clients connected or that have been connected to this appserver CountStatistic Low WritesBlockedCount ClientStats.WritesBlocked 556 Number of write operations that could not be completed immediately. For IBM Service use. All clients connected or that have been connected to this appserver CountStatistic Low WritesCount ClientStats.Writes 554 Number of write operations used to transmit data to client processes via network connections. All clients connected or that have been connected to this appserver CountStatistic Low To navigate to the counters in the admin console.
server_name | SIB Service | SIB Communications | Clients > Detailed Statistics
Name Key ID Description Granularity Type Level BytesReceivedAtHighPriorityCount ClientDetailedStats.BytesReceivedAtHighPriority 719 Number of bytes of data received at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtHighestPriorityCount ClientDetailedStats.BytesReceivedAtHighestPriority 717 Number of bytes of data received at the highest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS0PriorityCount ClientDetailedStats.BytesReceivedAtJMS0Priority 729 Number of bytes of data received at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS1PriorityCount ClientDetailedStats.BytesReceivedAtJMS1Priority 728 Number of bytes of data received at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS2PriorityCount ClientDetailedStats.BytesReceivedAtJMS2Priority 727 Number of bytes of data received at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS3PriorityCount ClientDetailedStats.BytesReceivedAtJMS3Priority 726 Number of bytes of data received at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS4PriorityCount ClientDetailedStats.BytesReceivedAtJMS4Priority 725 Number of bytes of data received at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS5PriorityCount ClientDetailedStats.BytesReceivedAtJMS5Priority 724 Number of bytes of data received at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS6PriorityCount ClientDetailedStats.BytesReceivedAtJMS6Priority 723 Number of bytes of data received at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS7PriorityCount ClientDetailedStats.BytesReceivedAtJMS7Priority 722 Number of bytes of data received at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS8PriorityCount ClientDetailedStats.BytesReceivedAtJMS8Priority 721 Number of bytes of data received at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS9PriorityCount ClientDetailedStats.BytesReceivedAtJMS9Priority 720 Number of bytes of data received at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtLowPriorityCount ClientDetailedStats.BytesReceivedAtLowPriority 730 Number of bytes of data received at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtLowestPriorityCount ClientDetailedStats.BytesReceivedAtLowestPriority 732 Number of bytes of data received at the lowest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtVeryHighPriorityCount ClientDetailedStats.BytesReceivedAtVeryHighPriority 718 Number of bytes of data received at a very high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtVeryLowPriorityCount ClientDetailedStats.BytesReceivedAtVeryLowPriority 731 Number of bytes of data received at a very low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtHighPriorityCount ClientDetailedStats.BytesSentAtHighPriority 703 Number of bytes of data transmitted at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtHighestPriorityCount ClientDetailedStats.BytesSentAtHighestPriority 701 Number of bytes of data transmitted at the highest possible priority for transmission. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS0PriorityCount ClientDetailedStats.BytesSentAtJMS0Priority 713 Number of bytes of data transmitted at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS1PriorityCount ClientDetailedStats.BytesSentAtJMS1Priority 712 Number of bytes of data transmitted at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS2PriorityCount ClientDetailedStats.BytesSentAtJMS2Priority 711 Number of bytes of data transmitted at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS3PriorityCount ClientDetailedStats.BytesSentAtJMS3Priority 710 Number of bytes of data transmitted at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS4PriorityCount ClientDetailedStats.BytesSentAtJMS4Priority 709 Number of bytes of data transmitted at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS5PriorityCount ClientDetailedStats.BytesSentAtJMS5Priority 708 Number of bytes of data transmitted at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS6PriorityCount ClientDetailedStats.BytesSentAtJMS6Priority 707 Number of bytes of data transmitted at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS7PriorityCount ClientDetailedStats.BytesSentAtJMS7Priority 706 Number of bytes of data transmitted at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS8PriorityCount ClientDetailedStats.BytesSentAtJMS8Priority 705 Number of bytes of data transmitted at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS9PriorityCount ClientDetailedStats.BytesSentAtJMS9Priority 704 Number of bytes of data transmitted at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtLowPriorityCount ClientDetailedStats.BytesSentAtLowPriority 714 Number of bytes of data transmitted at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtLowestPriorityCount ClientDetailedStats.BytesSentAtLowestPriority 716 Number of bytes of data transmitted at the lowest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtVeryHighPriorityCount ClientDetailedStats.BytesSentAtVeryHighPriority 702 Number of bytes of data transmitted at a very high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtVeryLowPriorityCount ClientDetailedStats.BytesSentAtVeryLowPriority 715 Number of bytes of data transmitted at a very low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS0PriorityCount ClientDetailedStats.MessagesReceivedAtJMS0Priority 752 Number of messages received at JMS priority 0. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS1PriorityCount ClientDetailedStats.MessagesReceivedAtJMS1Priority 751 Number of messages received at JMS priority 1. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS2PriorityCount ClientDetailedStats.MessagesReceivedAtJMS2Priority 750 Number of messages received at JMS priority 2. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS3PriorityCount ClientDetailedStats.MessagesReceivedAtJMS3Priority 749 Number of messages received at JMS priority 3. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS4PriorityCount ClientDetailedStats.MessagesReceivedAtJMS4Priority 748 Number of messages received at JMS priority 4. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS5PriorityCount ClientDetailedStats.MessagesReceivedAtJMS5Priority 747 Number of messages received at JMS priority 5. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS6PriorityCount ClientDetailedStats.MessagesReceivedAtJMS6Priority 746 Number of messages received at JMS priority 6. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS7PriorityCount ClientDetailedStats.MessagesReceivedAtJMS7Priority 745 Number of messages received at JMS priority 7. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS8PriorityCount ClientDetailedStats.MessagesReceivedAtJMS8Priority 744 Number of messages received at JMS priority 8. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS9PriorityCount ClientDetailedStats.MessagesReceivedAtJMS9Priority 743 Number of messages received at JMS priority 9. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS0PriorityCount ClientDetailedStats.MessagesSentAtJMS0Priority 742 Number of messages transmitted at JMS priority 0. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS1PriorityCount ClientDetailedStats.MessagesSentAtJMS1Priority 741 Number of messages transmitted at JMS priority 1. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS2PriorityCount ClientDetailedStats.MessagesSentAtJMS2Priority 740 Number of messages transmitted at JMS priority 2. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS3PriorityCount ClientDetailedStats.MessagesSentAtJMS3Priority 739 Number of messages transmitted at JMS priority 3. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS4PriorityCount ClientDetailedStats.MessagesSentAtJMS4Priority 738 Number of messages transmitted at JMS priority 4. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS5PriorityCount ClientDetailedStats.MessagesSentAtJMS5Priority 737 Number of messages transmitted at JMS priority 5. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS6PriorityCount ClientDetailedStats.MessagesSentAtJMS6Priority 736 Number of messages transmitted at JMS priority 6. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS7PriorityCount ClientDetailedStats.MessagesSentAtJMS7Priority 735 Number of messages transmitted at JMS priority 7. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS8PriorityCount ClientDetailedStats.MessagesSentAtJMS8Priority 734 Number of messages transmitted at JMS priority 8. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS9PriorityCount ClientDetailedStats.MessagesSentAtJMS9Priority 733 Number of messages transmitted at JMS priority 9. All clients connected or that have been connected to this appserver CountStatistic Low
To navigate to the counters in the admin console.
server_name | SIB Service | SIB Communications | Messaging Engines | Standard Statistics
Name Key ID Description Granularity Type Level APIConnectionsCount MEStats.APIConnections 502 Number of sessions being used by messaging engines that are currently network connected to this appserver. current applications servers hosting messaging engines/connections connected to this appserver. CountStatistic Low BufferedReadBytesCount MEStats.BufferedReadBytes 511 Number of bytes of data that have been received from the network and are held pending further processing. Large values might indicate that the appserver is unable to process data fast enough to keep up with the other appserver processes hosting messaging engines that it is network attached.
All messaging engines connected or that have been connected to this appserver CountStatistic Low BufferedWriteBytesCount MEStats.BufferedWriteBytes 510 Number of bytes of data being held pending transmission. Large values might indicate network congestion or appserver processes hosting messaging engines that are unable to process data fast enough to keep up with the appserver.
All messaging engines connected or that have been connected to this appserver CountStatistic Low ErrorsCount MEStats.Errors 503 Communication errors that have occurred and resulted in a network connection to a messaging engine being disconnected. All messaging engines connected or that have been connected to this appserver CountStatistic Low MEAttachedCount MEStats.MEAttached 501 Number of distinct appserver processes hosting messaging engines currently network connected to this application server. current applications servers hosting messaging engines/connections connected to this appserver. CountStatistic Low MessageBytesReadCount MEStats.MessageBytesRead 513 Number of bytes of message data received from application server processes hosting messaging engines over network connections. This does not include data used to negotiate the transmission of messages
All messaging engines connected or that have been connected to this appserver CountStatistic Low MessageBytesWrittenCount MEStats.MessageBytesWritten 512 Number of bytes of message data sent to application server processes hosting messaging engines over network connections. This does not include data used to negotiate the transmission of messages
All messaging engines connected or that have been connected to this appserver CountStatistic Low ReadsBlockedCount MEStats.ReadsBlocked 507 Number of read operations that could not be completed immediately. For IBM Service use. All messaging engines connected or that have been connected to this appserver CountStatistic Low ReadsCount MEStats.Reads 505 Number of read operations used to receive data from appserver processes hosting messaging engines via network connections. All messaging engines connected or that have been connected to this appserver CountStatistic Low TotalBytesReadCount MEStats.TotalBytesRead 515 Number of bytes of data received from appserver processes hosting messaging engines. All messaging engines connected or that have been connected to this appserver CountStatistic Low TotalBytesWrittenCount MEStats.TotalBytesWritten 514 Number of bytes of data sent to appserver processes hosting messaging engines. All messaging engines connected or that have been connected to this appserver CountStatistic Low WritesBlockedCount MEStats.WritesBlocked 506 Number of write operations that could not be completed immediately. For IBM Service use. All messaging engines connected or that have been connected to this appserver CountStatistic Low WritesCount MEStats.Writes 504 Number of write operations used to transmit data to appserver processes hosting messaging engines via network connections. All messaging engines connected or that have been connected to this appserver CountStatistic Low To navigate to the counters in the admin console.
server_name | SIB Service | SIB Communications | Messaging Engines | Detailed Statistics
Name Key ID Description Granularity Type Level BytesReceivedAtHighPriorityCount MEDetailedStats.BytesReceivedAtHighPriority 619 Number of bytes of data received at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected, or that have been connected, to this appserver CountStatistic Low BytesReceivedAtHighestPriorityCount MEDetailedStats.BytesReceivedAtHighestPriority 617 Number of bytes of data received at the highest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS0PriorityCount MEDetailedStats.BytesReceivedAtJMS0Priority 629 Number of bytes of data received at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS1PriorityCount MEDetailedStats.BytesReceivedAtJMS1Priority 628 Number of bytes of data received at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS2PriorityCount MEDetailedStats.BytesReceivedAtJMS2Priority 627 Number of bytes of data received at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS3PriorityCount MEDetailedStats.BytesReceivedAtJMS3Priority 626 Number of bytes of data received at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS4PriorityCount MEDetailedStats.BytesReceivedAtJMS4Priority 625 Number of bytes of data received at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS5PriorityCount MEDetailedStats.BytesReceivedAtJMS5Priority 624 Number of bytes of data received at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS6PriorityCount MEDetailedStats.BytesReceivedAtJMS6Priority 623 Number of bytes of data received at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS7PriorityCount MEDetailedStats.BytesReceivedAtJMS7Priority 622 Number of bytes of data received at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS8PriorityCount MEDetailedStats.BytesReceivedAtJMS8Priority 621 Number of bytes of data received at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtJMS9PriorityCount MEDetailedStats.BytesReceivedAtJMS9Priority 620 Number of bytes of data received at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All MEs connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtLowPriorityCount MEDetailedStats.BytesReceivedAtLowPriority 630 Number of bytes of data received at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtLowestPriorityCount MEDetailedStats.BytesReceivedAtLowestPriority 632 Number of bytes of data received at the lowest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtVeryHighPriorityCount MEDetailedStats.BytesReceivedAtVeryHighPriority 618 Number of bytes of data received at a very high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesReceivedAtVeryLowPriorityCount MEDetailedStats.BytesReceivedAtVeryLowPriority 631 Number of bytes of data received at a very low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtHighPriorityCount MEDetailedStats.BytesSentAtHighPriority 603 Number of bytes of data transmitted at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtHighestPriorityCount MEDetailedStats.BytesSentAtHighestPriority 601 Number of bytes of data transmitted at the highest possible priority for transmission. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS0PriorityCount MEDetailedStats.BytesSentAtJMS0Priority 613 Number of bytes of data transmitted at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS1PriorityCount MEDetailedStats.BytesSentAtJMS1Priority 612 Number of bytes of data transmitted at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS2PriorityCount MEDetailedStats.BytesSentAtJMS2Priority 611 Number of bytes of data transmitted at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS3PriorityCount MEDetailedStats.BytesSentAtJMS3Priority 610 Number of bytes of data transmitted at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS4PriorityCount MEDetailedStats.BytesSentAtJMS4Priority 609 Number of bytes of data transmitted at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS5PriorityCount MEDetailedStats.BytesSentAtJMS5Priority 608 Number of bytes of data transmitted at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS6PriorityCount MEDetailedStats.BytesSentAtJMS6Priority 607 Number of bytes of data transmitted at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS7PriorityCount MEDetailedStats.BytesSentAtJMS7Priority 606 Number of bytes of data transmitted at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS8PriorityCount MEDetailedStats.BytesSentAtJMS8Priority 605 Number of bytes of data transmitted at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtJMS9PriorityCount MEDetailedStats.BytesSentAtJMS9Priority 604 Number of bytes of data transmitted at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtLowPriorityCount MEDetailedStats.BytesSentAtLowPriority 614 Number of bytes of data transmitted at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtLowestPriorityCount MEDetailedStats.BytesSentAtLowestPriority 616 Number of bytes of data transmitted at the lowest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtVeryHighPriorityCount MEDetailedStats.BytesSentAtVeryHighPriority 602 Number of bytes of data transmitted at a very high priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low BytesSentAtVeryLowPriorityCount MEDetailedStats.BytesSentAtVeryLowPriority 615 Number of bytes of data transmitted at a very low priority. Message data cannot be transmitted with this priority, so typically these bytes of data will comprise control transmissions used to negotiate the flow of messages.
All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS0PriorityCount MEDetailedStats.MessagesReceivedAtJMS0Priority 652 Number of messages received at JMS priority 0. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS1PriorityCount MEDetailedStats.MessagesReceivedAtJMS1Priority 651 Number of messages received at JMS priority 1. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS2PriorityCount MEDetailedStats.MessagesReceivedAtJMS2Priority 650 Number of messages received at JMS priority 2. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS3PriorityCount MEDetailedStats.MessagesReceivedAtJMS3Priority 649 Number of messages received at JMS priority 3. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS4PriorityCount MEDetailedStats.MessagesReceivedAtJMS4Priority 648 Number of messages received at JMS priority 4. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS5PriorityCount MEDetailedStats.MessagesReceivedAtJMS5Priority 647 Number of messages received at JMS priority 5. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS6PriorityCount MEDetailedStats.MessagesReceivedAtJMS6Priority 646 Number of messages received at JMS priority 6. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS7PriorityCount MEDetailedStats.MessagesReceivedAtJMS7Priority 645 Number of messages received at JMS priority 7. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS8PriorityCount MEDetailedStats.MessagesReceivedAtJMS8Priority 644 Number of messages received at JMS priority 8. All clients connected or that have been connected to this appserver CountStatistic Low MessagesReceivedAtJMS9PriorityCount MEDetailedStats.MessagesReceivedAtJMS9Priority 643 Number of messages received at JMS priority 9. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS0PriorityCount MEDetailedStats.MessagesSentAtJMS0Priority 642 Number of messages transmitted at JMS priority 0. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS1PriorityCount MEDetailedStats.MessagesSentAtJMS1Priority 641 Number of messages transmitted at JMS priority 1. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS2PriorityCount MEDetailedStats.MessagesSentAtJMS2Priority 640 Number of messages transmitted at JMS priority 2. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS3PriorityCount MEDetailedStats.MessagesSentAtJMS3Priority 639 Number of messages transmitted at JMS priority 3. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS4PriorityCount MEDetailedStats.MessagesSentAtJMS4Priority 638 Number of messages transmitted at JMS priority 4. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS5PriorityCount MEDetailedStats.MessagesSentAtJMS5Priority 637 Number of messages transmitted at JMS priority 5. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS6PriorityCount MEDetailedStats.MessagesSentAtJMS6Priority 636 Number of messages transmitted at JMS priority 6. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS7PriorityCount MEDetailedStats.MessagesSentAtJMS7Priority 635 Number of messages transmitted at JMS priority 7. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS8PriorityCount MEDetailedStats.MessagesSentAtJMS8Priority 634 Number of messages transmitted at JMS priority 8. All clients connected or that have been connected to this appserver CountStatistic Low MessagesSentAtJMS9PriorityCount MEDetailedStats.MessagesSentAtJMS9Priority 633 Number of messages transmitted at JMS priority 9. All clients connected or that have been connected to this appserver CountStatistic Low
server_name > SIB Service > SIB Communications > Messaging Engines > Detailed Statistics
The same set of detailed statistics are available for messaging engines as is described for MEs.
To navigate to the counters in the admin console.
server_name | SIB Service | SIB Communications | WMQ Links | Standard Statistics
Name Key ID Description Granularity Type Level BatchesReceivedCount MQLinkStats.BatchesReceived 802 Number of batches of messages received from network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low BatchesSentCount MQLinkStats.BatchesSent 801 Number of batches of messages sent to network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low CommsErrorsCount MQLinkStats.CommsErrors 811 Number of communication errors that resulted in a network connection to a WebSphere MQ Queue Manager being disconnected. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low LongRetriesCount MQLinkStats.LongRetries 810 Number of long retries. This indicates the number of times channels were disconnected and could not be re-established for longer periods of time. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low MessagesReceivedCount MQLinkStats.MessagesReceived 804 Number of messages received from network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low MessagesSentCount MQLinkStats.MessagesSent 803 Number of messages sent to network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low QMAttachedCount MQLinkStats.QMAttached 812 Total number of WebSphere MQ Queue Managers currently network attached to this appserver WebSphere MQ Queue Managers that are currently attached CountStatistic Low ReadsBlockedCount MQLinkStats.ReadsBlocked 814 Number of read operations that could not be completed immediately. For IBM Service use. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low ReceiverBytesReceivedCount MQLinkStats.ReceiverBytesReceived 808 Number of bytes of data received by receiver channels from network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low ReceiverBytesSentCount MQLinkStats.ReceiverBytesSent 807 Number of bytes of data sent by receiver channels to network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low SenderBytesReceivedCount MQLinkStats.SenderBytesReceived 806 Number of bytes of data received by sender channels from network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low SenderBytesSentCount MQLinkStats.SenderBytesSent 805 Number of bytes of data sent by sender channels to network attached WebSphere MQ Queue Managers. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low ShortRetriesCount MQLinkStats.ShortRetries 809 Number of short retries. This indicates the number of times channels were disconnected and could not be re-established for short periods of time. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low WritesBlockedCount MQLinkStats.WritesBlocked 813 Number of write operations that could not be completed immediately. For IBM Service use. All WebSphere MQ Queue Managers that are or have been connected to this appserver CountStatistic Low
To navigate to the counters in the admin console.
server_name | SIB Service | SIB Communications | WMQ Client Links | Standard Statistics
Name Key ID Description Granularity Type Level APICallsServicedCount MQClientLinkStats.APICallsServiced 906 Number of MQ API call requests serviced on behalf of WebSphere MQ JMS clients. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low BatchesSentCount MQClientLinkStats.BatchesSent 901 Number of batches of messages sent to network attached MQJMS clients. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low BytesReceivedCount MQClientLinkStats.BytesReceived 905 Number of bytes of data received from network attached WebSphere MQ JMS clients. This includes bytes of message data as well as bytes of data used to control the flow of messages.
All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low BytesSentCount MQClientLinkStats.BytesSent 904 Number of bytes of data sent to network attached WebSphere MQ JMS clients. This includes bytes of message data as well as bytes of data used to control the flow of messages.
All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low ClientsAttachedCount MQClientLinkStats.ClientsAttached 908 The current number of WebSphere MQ JMS clients attached to this appserver. WebSphere MQ JMS clients that are currently attached. CountStatistic Low CommsErrorsCount MQClientLinkStats.CommsErrors 907 Number of errors that have cause connections to WebSphere MQ JMS clients to be dropped. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low MessagesReceivedCount MQClientLinkStats.MessagesReceived 903 Number of messages received from network attached WebSphere MQ JMS clients. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low MessagesSentCount MQClientLinkStats.MessagesSent 902 Number of messages sent to network attached WebSphere MQ JMS clients. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low ReadsBlockedCount MQClientLinkStats.ReadsBlocked 910 Number of read operations that could not be completed immediately. For IBM Service use. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low WritesBlockedCount MQClientLinkStats.WritesBlocked 909 Number of write operations that could not be completed immediately. For IBM Service use. All WebSphere MQ JMS clients that are or have been connected to this appserver CountStatistic Low
Related tasks
Monitor overall system health
Related
PMI data organization
Service integration bus counters