This information describes how to manage Java Messaging Server (JMS) destinations in Calendar Server by using the imqcmd command. For a complete list of imqcmd options, see the Command Utility chapter in the Sun Java System Message Queue 4.1 Administration Guide.
The JMS API enables messages to be specified as either PERSISTENT or NON_PERSISTENT. By default, Calendar Server JMS notification messages are delivered in PERSISTENT mode. Thus, you should monitor and purge JMS messages for cases when the destination’s accumulated messages are taking up too much of the system’s resources. Calendar Server uses the DavNotificationTopic JMS topic. For more information, see Using Calendar Server 7 Notifications.
Use the following tasks to use the JMS imqcmd command to work with JMS destinations:
- Change directories to the GlassFish Server imq/bin directory.
- List and display the metrics of the JMS topic used by the Calendar Server, DavNotificationTopic.
Occasionally, you might need to purge all messages queued at the DavNotificationTopic physical destination, if the destination’s accumulated messages are taking up too much of the system’s resources. Purging a physical destination deletes all messages queued at the destination. Consider pausing the destination to temporarily suspend the delivery of messages from producers to the destination previous to the purge operation. Also, take a snapshot of the metrics before and after you run the purge command.
- Run the following commands.
- To monitor a physical destination’s disk utilization, use the imqcmd metrics command with the dsk option.
You can also use the -b host:port option to specify a remote broker host name and port, for example, -b host1.example.com:7676.