BEA WebLogic Server 9.0 Domain Configuration Schema Reference

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

Super Types
{http://www.w3.org/2001/XMLSchema}int
|
+--{http://www.bea.com/ns/weblogic/90/domain} (restriction)

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.
Properties
This component is not nillable.

Model
<expiration-scan-interval>

</expiration-scan-interval>

Source
<xs:element minOccurs="0" name="expiration-scan-interval" nillable="false">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="2147483647"/>
</xs:restriction>
</xs:simpleType>
</xs:element>

BEA WebLogic Server 9.0 Domain Configuration Schema Reference

Copyright 2005 BEA Systems Inc. Complete WebLogic Server Documentation