Managing Calendar Server JMS Destinations

Skip to end of metadata
Go to start of metadata
Starting with Oracle Communications Unified Communications Suite 7.0.6, and Delegated Administrator and Calendar Server 7.0.5, the documentation for Connector for Microsoft Outlook 8.0.2, Contacts Server 8.0, Instant Messaging Server 9.0.2, Delegated Administrator, and Calendar Server 7.0.5 is available on the Oracle Documentation site at

Managing Calendar Server Java Messaging Server Destinations

This page contains information for Calendar Server and will not be updated in the future. For documentation beginning with Calendar Server, see the Oracle Technology Network site at:

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.


Calendar Server JMS Destinations Overview

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.

Using the imqcmd Command with Calendar Server

Use the following tasks to use the JMS imqcmd command to work with JMS destinations:

To List a JMS Destination's Metrics

  1. Change directories to the GlassFish Server imq/bin directory.
    For example:
  2. List and display the metrics of the JMS topic used by the Calendar Server, DavNotificationTopic.
    For example:

To Purge All Messages

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 Disk Utilization

  • To monitor a physical destination’s disk utilization, use the imqcmd metrics command with the dsk option.
    For example:

Accessing Remote Brokers Tip

You can also use the -b host:port option to specify a remote broker host name and port, for example, -b

calendarserver calendarserver Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.

The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.