Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS Distributed Topic: Configuration: Thresholds and Quotas

Configuration Options

Use this page to define the maximum message/byte quotas, the upper and lower message/byte thresholds, and the maximum allowable message size for this distributed queue.

If a JMS template is specified for members of this distributed queue, then the default values (for example, `-1`) imply that the value will come from the template. See also the JMS Server quota, threshold, and paging configurables.

#### Configuration Options

Name | Description
--- | ---
Bytes Maximum | The maximum bytes quota (between `0` and a positive 64-bit integer) that can be stored in this destination. The default value of -1 specifies that there is no WebLogic-imposed limit on the number of bytes that can be stored in the destination. However, excessive bytes volume can cause memory saturation, so this value should correspond to the total amount of available system memory relative to the rest of your application load. Range of Values: >= BytesThresholdHigh. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note: If a JMS template is used for distributed destination members, then this setting applies only to those specific members and not the distributed destination set as a whole. MBean Attribute: `JMSDestCommonMBean.BytesMaximum` Minimum value: `-1` Maximum value: `9223372036854775807`
Bytes Threshold High | The upper threshold value that triggers events based on the number of bytes stored in this JMS server. If the number of bytes exceeds this threshold, the following events are triggered : Log Messages - A message is logged on the server indicating a high threshold condition. Flow Control - If flow control is enabled, the destination becomes armed and instructs producers to begin decreasing their message flow. A value of -1 specifies that flow control and threshold log messages are disabled for the destination. Range of Values: Between 0 and a positive 64-bit integer; <= BytesMaximum; >BytesThresholdLow. Note: This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean Attribute: `JMSDestCommonMBean.BytesThresholdHigh` Minimum value: `-1` Maximum value: `9223372036854775807`
Bytes Threshold Low | The lower threshold value (between 0 and a positive 64-bit integer) that triggers events based on the number of bytes stored in this JMS server. If the number of bytes falls below this threshold, the following events are triggered: Log Messages - A message is logged on the server indicating that the threshold condition has cleared. Flow Control - If flow control is enabled, the destination becomes disarmed and instructs producers to begin increasing their message flow. A value of -1 specifies that bytes paging, flow control, and threshold log messages are disabled for this JMS server. Range of Values: < BytesThresholdHigh. Note: This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean Attribute: `JMSDestCommonMBean.BytesThresholdLow` Minimum value: `-1` Maximum value: `9223372036854775807`
Bytes Paging Enabled | This parameter has been deprecated. Paging is always enabled. The "MessageBufferSize" parameter on JMSServerMBean controls how much memory is used before paging kicks in. MBean Attribute: `JMSTemplateMBean.BytesPagingEnabled` Changes take effect after you redeploy the module or restart the server.
Messages Maximum | The maximum message quota (total amount of messages) that can be stored in this JMS server. The default value of -1 specifies that there is no WebLogic-imposed limit on the number of messages that can be stored. However, excessive message volume can cause memory saturation, so this value should correspond to the total amount of available system memory relative to the rest of your application load. Range of Values: >= MessagesThresholdHigh. Note: This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note: If a JMS template is used for distributed destination members, then this setting applies only to those specific members and not the distributed destination set as a whole. MBean Attribute: `JMSDestCommonMBean.MessagesMaximum` Minimum value: `-1` Maximum value: `9223372036854775807`
Messages Threshold High | The upper threshold value that triggers events based on the number of messages stored in this JMS server. If the number of messages exceeds this threshold, the following events are triggered: Log Messages - A message is logged on the server indicating a high threshold condition. Flow Control - If flow control is enabled, the destination becomes armed and instructs producers to begin decreasing their message flow. A value of -1 specifies that bytes paging, flow control, and threshold log messages are disabled for this JMS server. Range of Values: Between 0 and a positive 64-bit integer; <= MessagesMaximum; >MessagesThresholdLow. Note: This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean Attribute: `JMSDestCommonMBean.MessagesThresholdHigh` Minimum value: `-1` Maximum value: `9223372036854775807`
Messages Threshold Low | The lower threshold value that triggers events based on the number of messages stored in this JMS server. If the number of messages falls below this threshold, the following events are triggered: Log Messages - A message is logged on the server indicating that the threshold condition has cleared. Flow Control - If flow control is enabled, the destination becomes disarmed and instructs producers to begin increasing their message flow. A value of -1 specifies that bytes paging, flow control, and threshold log messages are disabled for this JMS server. Range of Values: Between 0 and a positive 64-bit integer; < MessagesThresholdHigh. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean Attribute: `JMSDestCommonMBean.MessagesThresholdLow` Minimum value: `-1` Maximum value: `9223372036854775807`
Maximum Message Size | The maximum size of a message in bytes that will be accepted from producers on this JMS server. The message size includes the message body, any user-defined properties, and the user-defined JMS header fields: `JMSCorrelationID` and `JMSType`. Producers sending messages that exceed the configured maximum message size for the JMS server receive a `ResourceAllocationException`. Range of Values: Between `0` and a positive 32-bit integer. The maximum message size is only enforced for the initial production of a message. Messages that are redirected to an error destination or forwarded to a member of a distributed destination are not checked for size. For instance, if a destination and its corresponding error destination are configured with a maximum message size of 128K bytes and 64K bytes, respectively, a message of 96K bytes could be redirected to the error destination (even though it exceeds the Range of Values: the 64K byte maximum), but a producer could not directly send the 96K byte message to the error destination. Note: This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean Attribute: `JMSDestCommonMBean.MaximumMessageSize` Minimum value: `0` Maximum value: `2147483647`
Messages Paging Enabled | This parameter has been deprecated. Paging is always enabled. The "MessageBufferSize" parameter on JMSServerMBean controls how much memory is used before paging kicks in. MBean Attribute: `JMSTemplateMBean.MessagesPagingEnabled` Changes take effect after you redeploy the module or restart the server.