Name

The name of this JMS server configuration. WebLogic Server uses an MBean to implement and persist the configuration.

MBean: weblogic.management.
configuration.
JMSServerMBean

Attribute: Name

Store

The persistent store (either a disk-based file or a JDBC-accessible database) for this JMS server, which will be used as a physical repository for storing persistent message data.

This store must not be the same as the paging store, or the same as the store for any other JMS server.

MBean: weblogic.management.
configuration.
JMSServerMBean

Attribute: Store

Paging Store

The name of the paging store for this JMS server, which is a dedicated JMS file store where message bodies can be temporarily paged out when the JMS server's message load reaches a specified threshold--if paging is enabled on the Thresholds & Quotas tab.

The paging store must not be the same as the non-paging store, or the same as the store for any other JMS server.

MBean: weblogic.management.
configuration.
JMSServerMBean

Attribute: PagingStore

Temporary Template

The name of the existing JMS template that is used by JMS applications to create all temporary destinations (queues or topics). The attribute values for a temporary destination are derived from this JMS template. If provided as part of the template, the Store attribute values are ignored because temporary destinations do not support persistent messaging.

Note: If this attribute is set to None, attempts to create a temporary destination will fail.

MBean: weblogic.management.
configuration.
JMSServerMBean

Attribute: TemporaryTemplate

Default: null

Expiration Scan Interval

The amount of time, in seconds, that the JMS server will pause between its cycles of scanning its destinations for expired messages to process (acccording to the specified Expiration Policy on the destinations). The default value is 30 seconds. A value of 0 indicates that active scanning is disabled. That is, expired messages are passively removed as they are discovered.

Setting this value to some very large value also effectively disables active scanning for expired messages from the system. Users will not receive expired messages, and any expired messages that are discovered are removed form the system. However, expired messages sitting in idle destinations (i.e., an inactive queue or disconnected durable subscriber) will not be removed and will continue to consume system resources.

The scanning and processing cycle for expired messages occurs as follows:

• After the specified waiting period, the JMS server devotes a separate thread to scan all of its local destinations for expired messages.

• After the scanning is completed, all discovered expired messages are processed according to the specified Expiration Policy on the destinations (Discard, Log, or Redirect).

• The entire process repeats after another specified waiting period.

Note: Since a new scan will not start until the current one is finished and the specified waiting period ends, an expired message could still remain in the system for the maximum scan waiting period plus the amount of time it takes to perform the scan and processing.

MBean: weblogic.management.
configuration.
JMSServerMBean

Attribute: ExpirationScanInterval

Units: seconds

Minimum: 0

Maximum: 2147483647

Default: 30

Dynamic: yes