All MIBs › BEA-WEBLOGIC-MIB › jmsServerBytesMaximum
jmsServerBytesMaximum
Module: BEA-WEBLOGIC-MIB
OID (symbolic): BEA-WEBLOGIC-MIB::jmsServerBytesMaximum
OID (numeric): 1.3.6.1.4.1.140.625.660.1.45
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The value of bytesMaximum. This is the maximum number of bytes that can be stored in the JMS Server at any one time.
What is jmsServerBytesMaximum?
This OID sets the total byte capacity across all queues on this server, preventing the combined destinations from consuming unlimited disk. It's a server-wide quota. Example: setting this to 100GB caps all messages on this server at 100GB combined.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.140.625.660.1.45 snmpwalk -v2c -c public <target> BEA-WEBLOGIC-MIB::jmsServerBytesMaximum
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.140.625.660.1.45.1 snmpget -v2c -c public <target> BEA-WEBLOGIC-MIB::jmsServerBytesMaximum.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::jmsServerBytesMaximum 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.45 | jmsServerBytesMaximum | BEA-WEBLOGIC-MIB |