JMS Template --> Configuration --> Thresholds & Quotas

JMS Template --> Configuration --> Thresholds & Quotas

Tasks Related Topics Attributes

Overview

This page allows you to define the maximum message/byte quotas, the upper and lower message/byte thresholds, the maximum allowable message size, and whether message and/or byte paging is enabled for destinations created from this JMS template. The configurable threshold and quota attributes for a JMS template are the same as those configured for a destination. However, if a destination that is using a JMS template specifies a non-default value for a Threshold & Quota attribute, that value is used instead. See also the JMS Server quota, threshold, and paging configuration settings.

Tasks

Creating a JMS Template

Related Topics

WebLogic JMS Fundamentals in Programming WebLogic JMS
Managing WebLogic JMS in Programming WebLogic JMS
Developing a WebLogic JMS Applicationin Programming WebLogic JMS

Attributes

Attribute Label

Description

Value Constraints
Bytes Maximum The maximum bytes quota (total amount of bytes) that can be stored in a topic or queue destination. The default value of -1 specifies that there is no WebLogic-imposed limit on the number of bytes that can be stored in a 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. Note: Configured quotas do not apply to expired or error (redelivery limit) messages that are redirected to an error destination. Such messages are still moved into an error destination even if that destination has reached its quotas.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: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: BytesMaximum Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Bytes Threshold High The upper threshold value that triggers events based on the number of bytes stored in a topic or queue destination. If the number of bytes exceeds this threshold, the triggered events are:
Log Messages - A message is logged on the server indicating a high threshold condition.

Bytes Paging - If bytes paging is enabled (and a paging store has been configured), then destination-level bytes paging is started.

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 the destination -- unless the destination setting overrides this template.Range of Values: <= BytesMaximum; >BytesThresholdLow This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note: Bytes paging cannot be dynamically disabled by resetting the value to -1. To dynamically disable paging, you could set the value to a very large number, so that paging would not be triggered.MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: BytesThresholdHigh Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Bytes Threshold Low The lower threshold value that triggers events based on the number of bytes stored in a topic or queue destination. If the number of bytes falls below this threshold, the triggered events are:
Log Messages - A message is logged on the server indicating that the threshold condition has cleared.

Bytes Paging - If bytes paging is enabled, paging is stopped (if paging is occurring).

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 the destination -- unless the destination setting overrides this template.Range of Values: < BytesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: BytesThresholdLow Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Bytes Paging Enabled Specifies whether bytes paging is enabled for a topic or queue destination. Paging allows for temporarily swapping message bodies out from memory when a destination's bytes load reaches a specified threshold.
If the check box is cleared (false), bytes paging is disabled for the template's destinations -- unless the destination setting overrides the template.

If the check box is selected, and if a paging store has been configured for the JMS Server, and both the BytesThresholdLow and BytesThresholdHigh attribute values are greater than -1, then bytes paging is enabled for the template's destinations -- unless the destination setting overrides the template.
Note: If no value is defined, then this setting defaults to false and bytes paging is disabled for the template's destinations -- unless the destination setting overrides the template. MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: BytesPagingEnabled Default: falseValid values:
true

false

Messages Maximum The maximum message quota (total amount of messages) that can be stored in a topic or queue destination. The default value of -1 specifies that there is no WebLogic-imposed limit on the number of messages that can be stored in the destination. 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. Note: Configured quotas do not apply to expired or error (redelivery limit) messages that are redirected to an error destination. Such messages are still moved into an error destination even if that destination has reached its quotas.Range of Values: >= MessagesThresholdHigh 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: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: MessagesMaximum Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Messages Threshold High The upper threshold value that triggers events based on the number of messages stored in a topic or queue destination. If the number of messages exceeds this threshold, the triggered events are:
Log Messages - A message is logged on the server indicating a high threshold condition.

Messages Paging - If messages paging is enabled (and a paging store has been configured), then destination-level messages paging is started.

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 messages paging, flow control, and threshold log messages are disabled for the destination -- unless the destination setting overrides this template. Range of Values: <= MessagesMaximum; >MessagesThresholdLow This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note: Messages paging cannot be dynamically disabled by resetting the value to -1. To dynamically disable paging, you could set the value to a very large number, so that paging would not be triggered.MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: MessagesThresholdHigh Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Messages Threshold Low The lower threshold value that triggers events based on the number of messages stored in a topic or queue destination. If the number of messages falls below this threshold, the triggered events are:
Log Messages - A message is logged on the server indicating that the threshold condition has cleared.

Messages Paging - If messages paging is enabled, paging is stopped (if paging is occurring).

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 messages paging, flow control, and threshold log messages are disabled for the destination -- unless the destination setting overrides this template.Range of Values: < MessagesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: MessagesThresholdLow Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Messages Paging Enabled Specifies whether messages paging is enabled for a topic or queue destination. Paging allows for temporarily swapping message bodies out from memory when a destination's message load reaches a specified threshold.
If the check box is cleared (false), messages paging is disabled for the template's destinations -- unless the destination setting overrides this template.

If the check box is selected (true), and if a paging store has been configured for the JMS Server, and both the MessagesThresholdLow and MessagesThresholdHigh attribute values are greater than -1, then messages paging is enabled for the template's destinations -- unless the destination setting overrides the template.
Note: If no value is defined, this setting defaults to false and messages paging is disabled for the template's destinations -- unless the destination setting overrides this template. MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: MessagesPagingEnabled Default: falseValid values:
true

false

Maximum Message Size The maximum allowable size for messages to be accepted from producers on this destination. The message size includes the message body, user-defined properties, and the user-defined JMS header fields: JMSCorrelationID and JMSType. The maximum message size is checked before messages are sent to a destination. Therefore, if a message exceeds the specified allowable size, it does not count against the destination's configured quota (bytes/messages maximum) or it's upper thresholds, since the message is immediately rejected.When a producer sends a message that exceeds the specified maximum message size for the destination, it will receive a JMS ResourceAllocation exception. 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 example, if a destination and its corresponding error destination are configured with a maximum message size of 128K and 64K, respectively, a message of 96K could be redirected to the error destination (even though it exceeds the 64K maximum), but a producer could not directly send the 96K message to the error destination. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: MaximumMessageSize Minimum: 0Maximum: 2147483647Default: 2147483647Dynamic: yes

Attribute Label	Description	Value Constraints
Bytes Maximum	The maximum bytes quota (total amount of bytes) that can be stored in a topic or queue destination. The default value of -1 specifies that there is no WebLogic-imposed limit on the number of bytes that can be stored in a 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. Note: Configured quotas do not apply to expired or error (redelivery limit) messages that are redirected to an error destination. Such messages are still moved into an error destination even if that destination has reached its quotas.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: weblogic.management. configuration. JMSTemplateMBeanAttribute: BytesMaximum	Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Bytes Threshold High	The upper threshold value that triggers events based on the number of bytes stored in a topic or queue destination. If the number of bytes exceeds this threshold, the triggered events are: Log Messages - A message is logged on the server indicating a high threshold condition. Bytes Paging - If bytes paging is enabled (and a paging store has been configured), then destination-level bytes paging is started. 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 the destination -- unless the destination setting overrides this template.Range of Values: <= BytesMaximum; >BytesThresholdLow This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note: Bytes paging cannot be dynamically disabled by resetting the value to -1. To dynamically disable paging, you could set the value to a very large number, so that paging would not be triggered.MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: BytesThresholdHigh	Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Bytes Threshold Low	The lower threshold value that triggers events based on the number of bytes stored in a topic or queue destination. If the number of bytes falls below this threshold, the triggered events are: Log Messages - A message is logged on the server indicating that the threshold condition has cleared. Bytes Paging - If bytes paging is enabled, paging is stopped (if paging is occurring). 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 the destination -- unless the destination setting overrides this template.Range of Values: < BytesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: BytesThresholdLow	Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Bytes Paging Enabled	Specifies whether bytes paging is enabled for a topic or queue destination. Paging allows for temporarily swapping message bodies out from memory when a destination's bytes load reaches a specified threshold. If the check box is cleared (false), bytes paging is disabled for the template's destinations -- unless the destination setting overrides the template. If the check box is selected, and if a paging store has been configured for the JMS Server, and both the BytesThresholdLow and BytesThresholdHigh attribute values are greater than -1, then bytes paging is enabled for the template's destinations -- unless the destination setting overrides the template. Note: If no value is defined, then this setting defaults to false and bytes paging is disabled for the template's destinations -- unless the destination setting overrides the template. MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: BytesPagingEnabled	Default: falseValid values: true false
Messages Maximum	The maximum message quota (total amount of messages) that can be stored in a topic or queue destination. The default value of -1 specifies that there is no WebLogic-imposed limit on the number of messages that can be stored in the destination. 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. Note: Configured quotas do not apply to expired or error (redelivery limit) messages that are redirected to an error destination. Such messages are still moved into an error destination even if that destination has reached its quotas.Range of Values: >= MessagesThresholdHigh 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: weblogic.management. configuration. JMSTemplateMBeanAttribute: MessagesMaximum	Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Messages Threshold High	The upper threshold value that triggers events based on the number of messages stored in a topic or queue destination. If the number of messages exceeds this threshold, the triggered events are: Log Messages - A message is logged on the server indicating a high threshold condition. Messages Paging - If messages paging is enabled (and a paging store has been configured), then destination-level messages paging is started. 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 messages paging, flow control, and threshold log messages are disabled for the destination -- unless the destination setting overrides this template. Range of Values: <= MessagesMaximum; >MessagesThresholdLow This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note: Messages paging cannot be dynamically disabled by resetting the value to -1. To dynamically disable paging, you could set the value to a very large number, so that paging would not be triggered.MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: MessagesThresholdHigh	Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Messages Threshold Low	The lower threshold value that triggers events based on the number of messages stored in a topic or queue destination. If the number of messages falls below this threshold, the triggered events are: Log Messages - A message is logged on the server indicating that the threshold condition has cleared. Messages Paging - If messages paging is enabled, paging is stopped (if paging is occurring). 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 messages paging, flow control, and threshold log messages are disabled for the destination -- unless the destination setting overrides this template.Range of Values: < MessagesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: MessagesThresholdLow	Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes
Messages Paging Enabled	Specifies whether messages paging is enabled for a topic or queue destination. Paging allows for temporarily swapping message bodies out from memory when a destination's message load reaches a specified threshold. If the check box is cleared (false), messages paging is disabled for the template's destinations -- unless the destination setting overrides this template. If the check box is selected (true), and if a paging store has been configured for the JMS Server, and both the MessagesThresholdLow and MessagesThresholdHigh attribute values are greater than -1, then messages paging is enabled for the template's destinations -- unless the destination setting overrides the template. Note: If no value is defined, this setting defaults to false and messages paging is disabled for the template's destinations -- unless the destination setting overrides this template. MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: MessagesPagingEnabled	Default: falseValid values: true false
Maximum Message Size	The maximum allowable size for messages to be accepted from producers on this destination. The message size includes the message body, user-defined properties, and the user-defined JMS header fields: JMSCorrelationID and JMSType. The maximum message size is checked before messages are sent to a destination. Therefore, if a message exceeds the specified allowable size, it does not count against the destination's configured quota (bytes/messages maximum) or it's upper thresholds, since the message is immediately rejected.When a producer sends a message that exceeds the specified maximum message size for the destination, it will receive a JMS ResourceAllocation exception. 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 example, if a destination and its corresponding error destination are configured with a maximum message size of 128K and 64K, respectively, a message of 96K could be redirected to the error destination (even though it exceeds the 64K maximum), but a producer could not directly send the 96K message to the error destination. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: MaximumMessageSize	Minimum: 0Maximum: 2147483647Default: 2147483647Dynamic: yes