All MIBs › BEA-WEBLOGIC-MIB › jmsServerExpirationScanInterval
jmsServerExpirationScanInterval
Module: BEA-WEBLOGIC-MIB
OID (symbolic): BEA-WEBLOGIC-MIB::jmsServerExpirationScanInterval
OID (numeric): 1.3.6.1.4.1.140.625.660.1.74
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: 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.
What is jmsServerExpirationScanInterval?
This OID sets how frequently the JMS server scans for expired messages to remove them, in seconds. A zero disables active scanning. Example: setting this to 3600 scans for expired messages every hour.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.140.625.660.1.74 snmpwalk -v2c -c public <target> BEA-WEBLOGIC-MIB::jmsServerExpirationScanInterval
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.140.625.660.1.74.1 snmpget -v2c -c public <target> BEA-WEBLOGIC-MIB::jmsServerExpirationScanInterval.1
Start monitoring BEA/Oracle WebLogic Server (Java EE application server) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BEA-WEBLOGIC-MIB::jmsServerExpirationScanInterval OID value, configure state conditions and alerts, and monitor any BEA/Oracle WebLogic Server (Java EE application server) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.140 | bea | BEA-WEBLOGIC-MIB |
| 1.3.6.1.4.1.140.625 | wls | BEA-WEBLOGIC-MIB |
| 1.3.6.1.4.1.140.625.660 | jmsServerTable | BEA-WEBLOGIC-MIB |
| 1.3.6.1.4.1.140.625.660.1 | jmsServerEntry | BEA-WEBLOGIC-MIB |
| 1.3.6.1.4.1.140.625.660.1.74 | jmsServerExpirationScanInterval | BEA-WEBLOGIC-MIB |