Administration Console Online Help

JMS quotas are used to control the allotment of system resources available to destinations. For example, you can specify the number of bytes or messages that a destination is allowed to store, or specify whether the quota can be shared be all destinations that refer to it.

Once you configure a quota, you can select it on the Thresholds and Quota page from within a destination resource, such as a queue, topic, distributed queue, distributed topic, or JMS template if you are using templates to configure your destinations.

To configure a quota:

In the Administration Console, navigate to the destination key resource that you want to configure:
- Navigate to JMS Resources in System Modules
- Navigate to JMS resources in an application module
On the Configuration page:
1. In Bytes Maximum, enter the total number of bytes that can be stored in a destination that uses this quota.
2. In Messages Maximum, enter the total number of messages that can be stored in a destination that uses this quota.
3. In Policy, select the delivery policy to determine whether to allow smaller message send requests to be satisfied before larger ones when a destination has exceeded its message quota. The default FIFO (first in, first out) policy blocks subsequent newer sender requests until there is enough space for the first request in line, or denies the newer requests with a quota exception if the newer requests time out. The Preemptive policy allows newer smaller send requests to preempt previous larger requests when there is sufficient space for smaller messages on the destination, but not sufficient space for the older larger requests.
4. In Shared, specify whether this quota is shared by destinations that refer to it.
5. Click OK.
For more information about these fields see Configuration Options.
Save your changes:
- Save Changes to JMS Resources in System Modules
- Save changes to JMS resources in an application module

Administration Console Online Help

Configure quotas for destinations