http://www.bea.com/ns/weblogic/920/domain
element expiration-scan-interval

Model

<expiration-scan-interval>annonymous type derived from int</expiration-scan-interval>

Disallowed substitutions (block)

none (extensions, restrictions and substitutions are allowed)

Substitution group exclusion (final)

none (extensions and restrictions are allowed)

Usage

Documentation

The number of seconds between this JMS server's cycles of scanning local destinations for expired messages. A value of 0 disables active scanning. A very large scan interval effectively disables active scanning.

With scanning disabled, users still do not receive expired messages and any expired messages that are discovered by other system activities are removed. However, expired messages sitting in idle destinations (such as an inactive queue or disconnected durable subscriber) are not removed and continue to consume system resources.

The scanning 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 located expired messages are processed according to the specified Expiration Policy on the destination (Discard, Log, or Redirect).

• The entire process repeats after another specified waiting period.

Note: Because a new scan does not start until the current one is finished and until 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.

Privileges: Read/Write

Default Value: 30

Minimum value: 0

Maximum value: 2147483647

MBean Attribute: JMSServerMBean.ExpirationScanInterval

Fundamental Facets

equality, numeric, bounded, totaly ordered, countable infinite value space

White Space Processing

collapse

Pattern Facet

[\-+]?[0-9]+

Digits Facets

fraction digits: 0