The amount of memory used to store message bodies in memory before they are paged out to disk. A value of -1 (the default) specifies that the server will automatically determine a size based on the maximum heap size of the JVM. This default will be set to either one-third the maximum heap size, or 512 megabytes, whichever is larger. The larger the buffer, the more memory JMS will consume when many messages are waiting on queues or topics. Once the buffer is surpassed, JMS may write message bodies to the directory specified by PagingDirectory in an effort to reduce memory usage below this buffer. Surpassing the buffer size does not stop the JMS server from accepting new messages. It is still possible to run out of memory if messages are arriving faster than they can be written to disk. Users with high messaging loads who wish to support the highest possible availability should consider setting a quota or setting a threshold and enabling flow control. Applies only to agents with sending capability. Paging is always supported. Updating the memory size resets the message count so that only requests arriving after the update are charged against the new memory size.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
The amount of memory used to store message bodies in memory before they are paged out to disk. A value of -1 (the default) specifies that the server will automatically determine a size based on the maximum heap size of the JVM. This default will be set to either one-third the maximum heap size, or 512 megabytes, whichever is larger. The larger the buffer, the more memory JMS will consume when many messages are waiting on queues or topics. Once the buffer is surpassed, JMS may write message bodies to the directory specified by PagingDirectory in an effort to reduce memory usage below this buffer. Surpassing the buffer size does not stop the JMS server from accepting new messages. It is still possible to run out of memory if messages are arriving faster than they can be written to disk. Users with high messaging loads who wish to support the highest possible availability should consider setting a quota or setting a threshold and enabling flow control. Applies only to agents with sending capability. Paging is always supported. Updating the memory size resets the message count so that only requests arriving after the update are charged against the new memory size.
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]
safAgentMessageBufferSize OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of memory used to store message bodies in memory before they are paged out to disk. A value of -1 (the default) specifies that the server will automatically determine a size based on the maximum heap size of the JVM. This default will be set to either one-third the maximum heap size, or 512 megabytes, whichever is larger. The larger the buffer, the more memory JMS will consume when many messages are waiting on queues or topics. Once the buffer is surpassed, JMS may write message bodies to the directory specified by PagingDirectory in an effort to reduce memory usage below this buffer. Surpassing the buffer size does not stop the JMS server from accepting new messages. It is still possible to run out of memory if messages are arriving faster than they can be written to disk. Users with high messaging loads who wish to support the highest possible availability should consider setting a quota or setting a threshold and enabling flow control. Applies only to agents with sending capability. Paging is always supported. Updating the memory size resets the message count so that only requests arriving after the update are charged against the new memory size." ::= { safAgentEntry 22 }
safAgentMessageBufferSize OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of memory used to store message bodies in memory before they are paged out to disk. A value of -1 (the default) specifies that the server will automatically determine a size based on the maximum heap size of the JVM. This default will be set to either one-third the maximum heap size, or 512 megabytes, whichever is larger. The larger the buffer, the more memory JMS will consume when many messages are waiting on queues or topics. Once the buffer is surpassed, JMS may write message bodies to the directory specified by PagingDirectory in an effort to reduce memory usage below this buffer. Surpassing the buffer size does not stop the JMS server from accepting new messages. It is still possible to run out of memory if messages are arriving faster than they can be written to disk. Users with high messaging loads who wish to support the highest possible availability should consider setting a quota or setting a threshold and enabling flow control. Applies only to agents with sending capability. Paging is always supported. Updating the memory size resets the message count so that only requests arriving after the update are charged against the new memory size." ::= { safAgentEntry 22 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.140.625.1035.1.1 | safAgentIndex | 0 | 0 | Index column |
| 1.3.6.1.4.1.140.625.1035.1.2 | safAgentObjectName | 0 | 0 | ObjectName column |
| 1.3.6.1.4.1.140.625.1035.1.3 | safAgentType | 0 | 0 | Returns the type of the MBean. |
| 1.3.6.1.4.1.140.625.1035.1.4 | safAgentForwardingPausedAtStartup | 0 | 0 | Specifies whether the agent is paused for forwarding messages at the startup time. When enabled, the sending agent forwards me… |
| 1.3.6.1.4.1.140.625.1035.1.5 | safAgentDefaultRetryDelayMultiplier | 0 | 0 | The factor used to multiply the previous delay time to calculate the next delay time to be used. Applies only to agents with… |
| 1.3.6.1.4.1.140.625.1035.1.6 | safAgentLoggingEnabled | 0 | 0 | Specifies whether a message is logged in the server log file when a message fails to be forwarded. If selected, this applies… |
| 1.3.6.1.4.1.140.625.1035.1.7 | safAgentBytesThresholdHigh | 0 | 0 | The upper threshold value that triggers events based on the number of bytes stored in the SAF agent. The default value of -1… |
| 1.3.6.1.4.1.140.625.1035.1.8 | safAgentWindowInterval | 0 | 0 | The maximum amount of time, in milliseconds, that a JMS sending agent will wait before forwarding messages in a single batch. … |
| 1.3.6.1.4.1.140.625.1035.1.9 | safAgentBytesMaximum | 0 | 0 | The maximum bytes quota (total amount of bytes) that can be stored in this SAF agent. The default value of -1 specifies that… |
| 1.3.6.1.4.1.140.625.1035.1.10 | safAgentServiceType | 0 | 0 | The type of service that this SAF agent provides. Range of Values: Sending-only, Receiving-only, or Both. |
| 1.3.6.1.4.1.140.625.1035.1.11 | safAgentMessagesThresholdLow | 0 | 0 | The low threshold that triggers events based on the number of messages stored in the SAF agent. The default value of -1 disa… |
| 1.3.6.1.4.1.140.625.1035.1.12 | safAgentMessagesThresholdHigh | 0 | 0 | The upper threshold that triggers events based on the number of messages stored in the SAF agent. The default value of -1 di… |
| 1.3.6.1.4.1.140.625.1035.1.13 | safAgentIncomingPausedAtStartup | 0 | 0 | Specifies whether the agent is paused for incoming messages at startup time. When enabled, the sending agent accepts new messa… |
| 1.3.6.1.4.1.140.625.1035.1.14 | safAgentReceivingPausedAtStartup | 0 | 0 | Specifies whether the agent is paused for receiving messages at the startup time. When enabled, the sending agent receives mes… |
| 1.3.6.1.4.1.140.625.1035.1.15 | safAgentMessagesMaximum | 0 | 0 | The maximum message quota (total amount of messages) that can be stored in this SAF agent. The default value of -1 specifies… |
| 1.3.6.1.4.1.140.625.1035.1.16 | safAgentName | 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… |
| 1.3.6.1.4.1.140.625.1035.1.17 | safAgentConversationIdleTimeMaximum | 0 | 0 | The maximum amount of time allowed before a sending side releases the resources used by a conversation. If there is no activ… |
| 1.3.6.1.4.1.140.625.1035.1.18 | safAgentDefaultRetryDelayMaximum | 0 | 0 | The maximum amount of time, in milliseconds, between two successive delivery retry attempts. Applies only to agents with sen… |
| 1.3.6.1.4.1.140.625.1035.1.19 | safAgentMaximumMessageSize | 0 | 0 | The maximum number of bytes allowed in individual messages on this SAF agent. The message size includes the message body, an… |
| 1.3.6.1.4.1.140.625.1035.1.20 | safAgentAcknowledgeInterval | 0 | 0 | The maximum interval between two successive acknowledgements sent by the receiving side. Applies only to agents with receivi… |
| 1.3.6.1.4.1.140.625.1035.1.21 | safAgentDeploymentOrder | 0 | 0 | A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the… |
| 1.3.6.1.4.1.140.625.1035.1.23 | safAgentWindowSize | 0 | 0 | For JMS messages, the number of messages in a batch. A sending agent waits to forward a message batch until the source destinat… |
| 1.3.6.1.4.1.140.625.1035.1.24 | safAgentDefaultTimeToLive | 0 | 0 | The default amount of time, in milliseconds, that the agent guarantees to reliably send messages. A value of 0 means the age… |
| 1.3.6.1.4.1.140.625.1035.1.25 | safAgentPagingDirectory | 0 | 0 | Specifies where message bodies are written when the size of the message bodies in the JMS server exceeds the message buffer siz… |
| 1.3.6.1.4.1.140.625.1035.1.26 | safAgentBytesThresholdLow | 0 | 0 | The lower threshold that triggers events based on the number of bytes stored in the SAF agent. The default value of -1 disa… |
| 1.3.6.1.4.1.140.625.1035.1.27 | safAgentDefaultRetryDelayBase | 0 | 0 | The amount of time, in milliseconds, between the original delivery attempt and the first retry. If RetryDelayMultiplier is s… |