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:
In Bytes Maximum, enter the total
number of bytes that can be stored in a destination that uses this
Maximum, enter the total number of messages that can be stored
in a destination that uses this quota.
Policy, select the delivery policy to determines
whether to deliver smaller messages before larger ones when a destination
has exceeded its message quota. The FIFO (first in, first out) policy
strictly enqueues all send requests for the same destination until there is
enough space for the first request in line. This prevents smaller messages
from being delivered when larger requests are already waiting for space. The
Preemptive policy does allow smaller send requests to preempt previous
larger ones when there is sufficient space for smaller messages on the
Shared, specify whether this quota is shared by
destinations that refer to it.