Configure JMS server thresholds and quota

Before you begin

Create JMS servers

After you create a JMS server, you can define the upper and lower byte and/or message thresholds for destinations in JMS modules that targeted to this JMS server. Exceeding these thresholds will trigger events such as generating log messages and starting message flow control. In the Quota section, you can specify a maximum size allowed for messages and the number of messages and/or bytes available to a JMS server. You can also select a blocking policy to determine whether the JMS server delivers smaller messages before larger ones when a destination has exceeded its maximum number of messages.

To configure thresholds and quotas for a JMS server:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the Administration Console, expand Services > Messaging and select JMS Servers.
On the Summary of JMS Servers page, click the JMS server you want to configure.
Click the Configuration > Thresholds and Quotas tab.
To define thresholds for destinations targeted to this JMS server:
1. In Bytes Threshold High or Messages Threshold High, specify an upper threshold value that will trigger events based on the number of bytes or messages stored in this JMS server. Events include message flow control and system log messages.
2. In Bytes Threshold Low or Messages Threshold Low, specify a lower threshold value that will trigger events based on the number of bytes or messages stored in this JMS server. Events include message flow control and system log messages.
For more information about these fields, refer to Configuration Options.
To define quota for destinations targeted to this JMS server:
1. In Bytes Maximum or Messages Maximum, specify the maximum number of bytes or messages that can be stored in this JMS server. A value of -1 removes any WebLogic Server limits.
2. In Blocking Send Policy, select the JMS server's policy on whether to deliver smaller messages before larger ones when a destination has exceeded its message quota. FIFO prevents the JMS server from delivering smaller messages when larger ones are already waiting for space. Preemptive allows smaller send requests to preempt previous larger ones when there is sufficient space for smaller messages on the destination.
3. In Maximum Message Size, specify the maximum size of a message that will be accepted from message producers on this JMS server. The size includes the message body, any user-defined properties, and the user-defined JMS header fields, JMSCorrelationID and JMSType.
For more information about these fields, refer to Configuration Options.
Click Save.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).

Result