This tab defines the bytes/messages threshold and quota configuration attributes for a JMS topic. After defining a JMS server, you can configure its topics. You can configure one or more topics for each JMS server.

Note: You configure destinations explicitly or by configuring a JMS template that can be used to define multiple destinations with similar attribute settings, as described in JMS Template Tasks.

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. JMSTopicMBean 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. JMSTopicMBean 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. JMSTopicMBean Attribute: BytesThresholdLow	Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Bytes Paging Enabled	Return one of "true", "false", or "default". Flag for specifying whether or not bytes paging is enabled on the destination: If this flag is not selected (false), then bytes paging is explicitly disabled for this destination. If this flag is not 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 this destination. If this attribute is set to "default", then this value inherits the JMS template's value--if a JMS template is specified. If no template is configured for the destination, then the Default value is equivalent to False. MBean: weblogic.management. configuration. JMSTopicMBean Attribute: BytesPagingEnabled	Default: default Valid values: default false true Configurable: yes 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. JMSTopicMBean 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. JMSTopicMBean 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. JMSTopicMBean Attribute: MessagesThresholdLow	Minimum: -1 Maximum: 9223372036854775807 Default: -1 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Messages Paging Enabled	Return one of "true", "false", or "default". Flag for specifying whether or not messages paging is enabled on the destination: If this flag is not selected (false), then messages paging is explicitly disabled for this destination. If this flag is not 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 this destination. If this attribute is set to "default", then this value inherits the JMS template's value--if a JMS template is specified. If no template is configured for the destination, then the Default value is equivalent to False. MBean: weblogic.management. configuration. JMSTopicMBean Attribute: MessagesPagingEnabled	Default: default Valid values: default false true Configurable: yes Readable: yes Writable: yes

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.
JMSTopicMBean

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.
JMSTopicMBean

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.
JMSTopicMBean

Attribute: BytesThresholdLow

Minimum: -1

Maximum: 9223372036854775807

Default: -1

Configurable: yes

Dynamic: yes

Readable: yes

Writable: yes

Bytes Paging Enabled

Return one of "true", "false", or "default".

Flag for specifying whether or not bytes paging is enabled on the destination:

If this flag is not selected (false), then bytes paging is explicitly disabled for this destination.

If this flag is not 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 this destination.

If this attribute is set to "default", then this value inherits the JMS template's value--if a JMS template is specified. If no template is configured for the destination, then the Default value is equivalent to False.

MBean: weblogic.management.
configuration.
JMSTopicMBean

Attribute: BytesPagingEnabled

Default: default

Valid values:

default

false

true

Configurable: yes

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.
JMSTopicMBean

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.
JMSTopicMBean

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.
JMSTopicMBean

Attribute: MessagesThresholdLow

Minimum: -1

Maximum: 9223372036854775807

Default: -1

Configurable: yes

Dynamic: yes

Readable: yes

Writable: yes

Messages Paging Enabled

Return one of "true", "false", or "default".

Flag for specifying whether or not messages paging is enabled on the destination:

If this flag is not selected (false), then messages paging is explicitly disabled for this destination.

If this flag is not 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 this destination.

If this attribute is set to "default", then this value inherits the JMS template's value--if a JMS template is specified. If no template is configured for the destination, then the Default value is equivalent to False.

MBean: weblogic.management.
configuration.
JMSTopicMBean

Attribute: MessagesPagingEnabled

Default: default

Valid values:

default

false

true

Configurable: yes

Readable: yes

Writable: yes