BEA-WEBLOGIC-MIB :: jmsServerMaximumMessageSize

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBEA-WEBLOGIC-MIBjmsServerMaximumMessageSize

jmsServerMaximumMessageSize

Module: BEA-WEBLOGIC-MIB

OID (symbolic): BEA-WEBLOGIC-MIB::jmsServerMaximumMessageSize

OID (numeric): 1.3.6.1.4.1.140.625.660.1.77

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The maximum number of bytes allowed in individual messages on this JMS server. The size of a message includes the message body, any user-defined properties, and the user-defined JMS header fields JMSCorrelationID and JMSType. The maximum message size is only enforced for the initial production of a message. Messages that are redirected to an error destination or forwarded to a member of a distributed destination are not checked for size. For instance, if a destination and its corresponding error destination are configured with a maximum message size of 128K bytes and 64K bytes, respectively, a message of 96K bytes could be redirected to the error destination (even though it exceeds the 64K byte maximum), but a producer could not directly send the 96K byte message to the error destination. Note: Any change to this maximum affects only incoming messages; stored messages are not affected.

What is jmsServerMaximumMessageSize?

This OID specifies the largest single message (in bytes) allowed on this server, including headers and properties. It prevents oversized messages from consuming memory. Example: setting this to 10485760 limits messages to 10MB.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.140.625.660.1.77
snmpwalk -v2c -c public <target> BEA-WEBLOGIC-MIB::jmsServerMaximumMessageSize

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.140.625.660.1.77.1
snmpget -v2c -c public <target> BEA-WEBLOGIC-MIB::jmsServerMaximumMessageSize.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::jmsServerMaximumMessageSize 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.140beaBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625wlsBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.660jmsServerTableBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.660.1jmsServerEntryBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.660.1.77jmsServerMaximumMessageSizeBEA-WEBLOGIC-MIB