BEA-WEBLOGIC-MIB :: webAppContainerFilterDispatchedRequestsEnabled

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBEA-WEBLOGIC-MIBwebAppContainerFilterDispatchedRequestsEnabled

webAppContainerFilterDispatchedRequestsEnabled

Module: BEA-WEBLOGIC-MIB

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

OID (numeric): 1.3.6.1.4.1.140.625.1155.1.10

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Indicates whether or not to apply filters to dispatched requests. This is a backward compatibility flag. Until version 8.1, WebLogic Server applied ServletFilters (if configured for the Web application) on request dispatches (and includes/forwards). Servlet 2.4 has introduced the 'Dispatcher' element to make this behavior explicit. The default value is Dispatcher=REQUEST. In order to be complaint with the J2EE specification, the default value for FilterDispatchedRequestsEnabled is false beginning with WebLogic Server 9.0. Note that if you are using old descriptors (meaning web.xml does not have version=2.4), then WebLogic Server automatically uses FilterDispatchedRequestsEnabled = true for the Web applications, unless filter-dispatched-requests-enabled is explicitly set to false in weblogic.xml. This means that old applications will work fine without any modification. Additionally, during migration of old domains to the 9.0 domain, the migration plugin automatically sets this flag to true.

What is webAppContainerFilterDispatchedRequestsEnabled?

Controls whether servlet filters are applied to dispatched requests (includes/forwards), which is disabled by default per Servlet 2.4 spec. Enabling provides backward compatibility. Example: enabling this applies filters to every included request, matching behavior from WebLogic 8.1 and earlier.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.140.625.1155.1.10
snmpwalk -v2c -c public <target> BEA-WEBLOGIC-MIB::webAppContainerFilterDispatchedRequestsEnabled

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.140.625.1155.1.10.1
snmpget -v2c -c public <target> BEA-WEBLOGIC-MIB::webAppContainerFilterDispatchedRequestsEnabled.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> webAppContainerFilterDispatchedRequestsEnabled.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::webAppContainerFilterDispatchedRequestsEnabled 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.1155webAppContainerTableBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.1155.1webAppContainerEntryBEA-WEBLOGIC-MIB
1.3.6.1.4.1.140.625.1155.1.10webAppContainerFilterDispatchedRequestsEnabledBEA-WEBLOGIC-MIB