Monitor JMS servers

On the JMS Server: Monitoring page, you can monitor statistics for view runtime information for an active JMS server. From here, you can also access runtime information for a JMS server's destinations, transactions, connections, and server session pools.

In the Administration Console, expand Services > Messaging and select JMS Servers.
On the Summary of JMS Servers page, click the JMS server that you want to monitor.
Click the Monitoring tab to display the monitoring links for monitoring JMS server data:
1. Monitoring - A table displays all instances of the JMS server deployed across the domain.
2. Active Destinations - A table displays statistics for all active JMS destinations for the domain. For troubleshooting purposes, run-time message production, consumption, and insertion activity can be temporarily paused on any or all destinations. Simply select a destination(s), and then click either the Production, Consumption, or Insertion button above the table to select a Pause or Resume operation. The table then reflects the destination's new "paused" or "non-paused" state.
  For more information, see Monitoring Options.
3. Active Transactions - A table displays all active JMS transactions for the domain. For troubleshooting purposes, you can force commits or rollbacks on selected transactions. Simply select a transaction(s), and then click either the Force Commit or Force Rollback button above the table to initiate a commit or rollback operation. The table then reflects the transaction's new status.
  For more information, see Monitoring Options.
4. Active Connections - A table displays showing all active JMS connections for the domain. For troubleshooting purposes, you can destroy selected connections. Simply select a connection(s), and then click the Destroy button above the table. The table then reflects the connection's new status.
  For more information, see Monitoring Options.
5. Active Session Pools - A table displays showing all active JMS session pools for the domain.
  For more information, see Monitoring Options.
For more information about monitoring JMS objects, see Monitoring JMS .

} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i