bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS Distributed Topic --> Configuration --> Thresholds and Quotas

Tasks Additional Documentation Attributes

Overview

This tab defines the bytes/messages threshold and quota configuration attributes for a set of JMS distributed topics.

Tasks

Create a JMS Distributed Topic

Delete a JMS Distributed Topic

Additional Documentation

(Requires an Internet connection.)

"Developing a WebLogic JMS Application"in Programming WebLogic JMS

"Managing JMS" in the Administration Guide

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Bytes Maximum | The value of BytesMaximum. The maximum number of bytes that may be stored in the destination. A value of -1 specifies that there is no limit on the number of bytes that can be stored in the destination. 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. Range of Values: >= BytesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: BytesMaximum | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Bytes Threshold High | The value of BytesThresholdHigh. Upper threshold value that triggers events based on the number of bytes stored in the 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. Range of Values:<= BytesMaximum; >BytesThresholdLow This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note:If bytes paging is enabled, it cannot be dynamically disabled by resetting the BytesThresholdHigh to -1, as this will cause an exception to be thrown. To dynamically disable paging, you could set the BytesThresholdHigh to a very large number, so that paging would not be triggered. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: BytesThresholdHigh | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Bytes Threshold Low | The value of BytesThresholdLow. Lower threshold value that triggers events based on the number of bytes stored in the 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. Range of Values: < BytesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: BytesThresholdLow | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Bytes Paging Enabled | Check if BytesPagingEnabled is set. Flag for specifying whether or not bytes paging is enabled on the template: If this flag is not selected (false), then bytes paging is disabled for the template's destinations-unless the destination setting overrides the template. If this flag is selected (true), 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. JMSTemplateMBean Attribute: BytesPagingEnabled | Default: false Readable: yes Writable: yes
Messages Maximum | The value of MessagesMaximum. The maximum number of messages that may be stored in the destination. A value of -1 specifies that there is no limit on the number of messages that can be stored in the destination. 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. Range of Values: >= MessagesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: MessagesMaximum | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Messages Threshold High | The value of MessagesThresholdHigh. Upper threshold value that triggers events based on the number of messages stored in the 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. Bytes 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. Range of Values:<= MessagesMaximum; >MessagesThresholdLow This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. Note:If messages paging is enabled, it cannot be dynamically disabled by resetting the MessagesThresholdHigh to -1, as this will cause an exception to be thrown. To dynamically disable paging, you could set the MessagesThresholdHigh to a very large number, so that paging would not be triggered. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: MessagesThresholdHigh | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Messages Threshold Low | The value of MessagesThresholdLow. Lower threshold value that triggers events based on the number of messages stored in the 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. Bytes 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. Range of Values: < MessagesThresholdHigh This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: MessagesThresholdLow | Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Messages Paging Enabled | Check if MessagesPagingEnabled is set. Flag for specifying whether or not messages paging is enabled on the template: If this flag is not selected (false), then messages paging is disabled for the template's destinations-unless the destination setting overrides the template. If this flag is selected (true), 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 the template. MBean: weblogic.management. configuration. JMSTemplateMBean Attribute: MessagesPagingEnabled | Default: false Readable: yes Writable: yes