Specifies the freshness policy for received messages: the Web Serivce observes the processing delay by subtracting the Created time in the Timestamp from the current time. If the observed processing delay is greater than maxProcessingDelay plus clockSkew, then the message is rejected as stale. This attribute is specified in milliseconds. Setting maxProcessingDelay to NO_MAX_PROCESSING_DELAY disables to enforcement of the freshenss policy.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
Specifies the freshness policy for received messages: the Web Serivce observes the processing delay by subtracting the Created time in the Timestamp from the current time. If the observed processing delay is greater than maxProcessingDelay plus clockSkew, then the message is rejected as stale. This attribute is specified in milliseconds. Setting maxProcessingDelay to NO_MAX_PROCESSING_DELAY disables to enforcement of the freshenss policy.
Parsed from file BEA-WEBLOGIC-MIB.mib
Module: BEA-WEBLOGIC-MIB
Vendor: Independence Technologies, Inc.(ITI)
Module: BEA-WEBLOGIC-MIB
[Automatically extracted from oidview.com]
webserviceTimestampMaxProcessingDelay OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the freshness policy for received messages: the Web Serivce observes the processing delay by subtracting the Created time in the Timestamp from the current time. If the observed processing delay is greater than maxProcessingDelay plus clockSkew, then the message is rejected as stale. This attribute is specified in milliseconds. Setting maxProcessingDelay to NO_MAX_PROCESSING_DELAY disables to enforcement of the freshenss policy." ::= { webserviceTimestampEntry 4 }
webserviceTimestampMaxProcessingDelay OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the freshness policy for received messages: the Web Serivce observes the processing delay by subtracting the Created time in the Timestamp from the current time. If the observed processing delay is greater than maxProcessingDelay plus clockSkew, then the message is rejected as stale. This attribute is specified in milliseconds. Setting maxProcessingDelay to NO_MAX_PROCESSING_DELAY disables to enforcement of the freshenss policy." ::= { webserviceTimestampEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.140.625.1185.1.1 | webserviceTimestampIndex | 0 | 0 | Index column |
| 1.3.6.1.4.1.140.625.1185.1.2 | webserviceTimestampObjectName | 0 | 0 | ObjectName column |
| 1.3.6.1.4.1.140.625.1185.1.3 | webserviceTimestampType | 0 | 0 | Returns the type of the MBean. |
| 1.3.6.1.4.1.140.625.1185.1.5 | webserviceTimestampClockSkew | 0 | 0 | ClockSkew takes precedence over ClockPrecision if both are defined, as ClockPrecision has been DEPRECATED. If clocks are synchr… |
| 1.3.6.1.4.1.140.625.1185.1.6 | webserviceTimestampClockSynchronized | 0 | 0 | Specifies whether the Web Service assumes synchronized clocks. If the clockSynchronized attribute is false, the Web Service re… |
| 1.3.6.1.4.1.140.625.1185.1.7 | webserviceTimestampClockPrecision | 0 | 0 | None |
| 1.3.6.1.4.1.140.625.1185.1.8 | webserviceTimestampValidityPeriod | 0 | 0 | Represents the length of time the sender wants the outbound message to be valid. When the validityPeriod is positive, the Tim… |
| 1.3.6.1.4.1.140.625.1185.1.9 | webserviceTimestampLaxPrecision | 0 | 0 | DEPRECATED. |
| 1.3.6.1.4.1.140.625.1185.1.10 | webserviceTimestampName | 0 | 0 | The user-specified name of this MBean instance. This name is included as one of the key properties in the MBean's javax.manage… |