bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS Server --> Configuration --> Thresholds & Quotas

Tasks Additional Documentation Attributes

Overview

This tab defines threshold and quota attributes for an instance of a JMS server. A JMS server manages connections and message requests on behalf of clients. You must first configure a JMS server before you can configure any destinations or consumers.

Tasks

Create a JMS Server

Clone a JMS Server

Delete a JMS Server

Assign a JMS Server

Additional Documentation

(Requires an Internet connection.)

"Managing JMS"in the Administration Guide

"Managing WebLogic JMS" in Programming WebLogic JMS

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Bytes Maximum | The value of BytesMaximum. The maximum number of bytes that may be stored in the JMS server. A value of -1 specifies that there is no limit on the number of bytes that can be stored in the JMS server. Range of Values: >= BytesThresholdHigh This attribute is dynamically configurable. MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server. 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 server bytes paging is started. Flow Control - If flow control is enabled, the JMS server becomes armed and instructs producers to begin decreasing their message flow. A value of -1 specifies that server bytes paging, flow control, and threshold log messages are disabled for the JMS server. Range of Values:<= BytesMaximum; >BytesThresholdLow This attribute is dynamically configurable. Note:Bytes paging cannot be dynamically disabled by resetting the BytesThresholdHigh to -1. To disable paging, you could set the BytesThresholdHigh to a very large number, so that paging would not be triggered. MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server. 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 JMS server becomes disarmed and instructs producers to begin increasing their message flow. A value of -1 specifies that server bytes paging, flow control, and threshold log messages are disabled for the JMS server. Range of Values: < BytesThresholdHigh This attribute is dynamically configurable. MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server: If this flag is not selected (false), then server bytes paging is explicitly disabled. If this flag is selected (true), a paging store has been configured, and both the BytesThresholdLow and BytesThresholdHigh attribute values are greater than -1, then server bytes paging is enabled. If either the BytesThresholdLow or BytesThreshold Highattribute is undefined, or defined as -1, then server bytes paging is implicitly disabled--even though this flag is selected. MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server. A value of -1 specifies that there is no limit on the number of messages that can be stored in the JMS server. This attribute is dynamically configurable. Range of Values:>= MessagesThresholdHigh MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server. 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 server messages paging is started. Flow Control - If flow control is enabled, the JMS server becomes armed and instructs producers to begin decreasing their message flow. A value of -1 specifies that server messages paging, flow control, and threshold log messages are disabled for the JMS server. Range of Values:<= MessagesMaximum; >MessagesThresholdLow This attribute is dynamically configurable. Note:Messages paging cannot be dynamically disabled by resetting the MessagesThresholdHigh to -1. To disable paging, you could set the MessagesThresholdHigh to a very large number, so that paging would not be triggered. MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server. 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 JMS server becomes disarmed and instructs producers to begin increasing their message flow. A value of -1 specifies that server messages paging, flow control, and threshold log messages are disabled for the JMS server. Range of Values: < MessagesThresholdHigh This attribute is dynamically configurable. MBean: weblogic.management. configuration. JMSServerMBean 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 JMS server: If this flag is not selected (false), then server messages paging is explicitly disabled. If this flag is selected (true), a paging store has been configured, and both the MessagesThresholdLow and MessagesThresholdHigh attribute values are greater than -1, then server messages paging is enabled. If either the MessagesThresholdLow or MessagesThresholdHigh attribute is undefined, or defined as -1, then server messages paging is implicitly disabled--even though this flag is selected. MBean: weblogic.management. configuration. JMSServerMBean Attribute: MessagesPagingEnabled | Default: false Readable: yes Writable: yes