Determines whether the JMS server delivers smaller messages before larger ones when a destination has exceeded its maximum number of messages. FIFO prevents the JMS server from delivering smaller messages when larger ones are already waiting for space. Preemptive allows smaller send requests to preempt previous larger ones when there is sufficient space for smaller messages on the destination. This policy is defined only for the JMS server; it cannot be set on individual destinations. Additional information on the FIFO and Preemptive policies is provided below. FIFO (first in, first out) indicates that all send requests for the same destination are queued up one behind the other until space is available. No send request is permitted to successfully complete if there is another send request waiting for space before it. When space is limited, the FIFO policy prevents the starvation of larger requests because smaller requests cannot continuously use the remaining available space. Smaller requests are delayed, though not starved, until the larger request can be completed. When space does become available, requests are considered in the order in which they were made. If there is sufficient space for a given request, then that request is completed and the next request is considered. If there is insufficient space for a given request, then no further requests are considered until sufficient space becomes available for the current request to complete. Preemptive indicates that a send operation can preempt other blocking send operations if space is available. That is, if there is sufficient space for the current request, then that space is used even if there are other requests waiting for space. When space is limited, the Preemptive policy can result in the starvation of larger requests. For example, if there is insufficient available space for a large request, then it is queued up behind other existing requests. When space does become available, all requests are considered in the order in which they were originally made. If there is sufficient space for a given request, then that request is allowed to continue and the next request is considered. If there is insufficient space for a given request, then that request is skipped and the next request is considered.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
Determines whether the JMS server delivers smaller messages before larger ones when a destination has exceeded its maximum number of messages. FIFO prevents the JMS server from delivering smaller messages when larger ones are already waiting for space. Preemptive allows smaller send requests to preempt previous larger ones when there is sufficient space for smaller messages on the destination. This policy is defined only for the JMS server; it cannot be set on individual destinations. Additional information on the FIFO and Preemptive policies is provided below. FIFO (first in, first out) indicates that all send requests for the same destination are queued up one behind the other until space is available. No send request is permitted to successfully complete if there is another send request waiting for space before it. When space is limited, the FIFO policy prevents the starvation of larger requests because smaller requests cannot continuously use the remaining available space. Smaller requests are delayed, though not starved, until the larger request can be completed. When space does become available, requests are considered in the order in which they were made. If there is sufficient space for a given request, then that request is completed and the next request is considered. If there is insufficient space for a given request, then no further requests are considered until sufficient space becomes available for the current request to complete. Preemptive indicates that a send operation can preempt other blocking send operations if space is available. That is, if there is sufficient space for the current request, then that space is used even if there are other requests waiting for space. When space is limited, the Preemptive policy can result in the starvation of larger requests. For example, if there is insufficient available space for a large request, then it is queued up behind other existing requests. When space does become available, all requests are considered in the order in which they were originally made. If there is sufficient space for a given request, then that request is allowed to continue and the next request is considered. If there is insufficient space for a given request, then that request is skipped and the next request is considered.
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]
jmsServerBlockingSendPolicy OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Determines whether the JMS server delivers smaller messages before larger ones when a destination has exceeded its maximum number of messages. FIFO prevents the JMS server from delivering smaller messages when larger ones are already waiting for space. Preemptive allows smaller send requests to preempt previous larger ones when there is sufficient space for smaller messages on the destination. This policy is defined only for the JMS server; it cannot be set on individual destinations. Additional information on the FIFO and Preemptive policies is provided below. FIFO (first in, first out) indicates that all send requests for the same destination are queued up one behind the other until space is available. No send request is permitted to successfully complete if there is another send request waiting for space before it. When space is limited, the FIFO policy prevents the starvation of larger requests because smaller requests cannot continuously use the remaining available space. Smaller requests are delayed, though not starved, until the larger request can be completed. When space does become available, requests are considered in the order in which they were made. If there is sufficient space for a given request, then that request is completed and the next request is considered. If there is insufficient space for a given request, then no further requests are considered until sufficient space becomes available for the current request to complete. Preemptive indicates that a send operation can preempt other blocking send operations if space is available. That is, if there is sufficient space for the current request, then that space is used even if there are other requests waiting for space. When space is limited, the Preemptive policy can result in the starvation of larger requests. For example, if there is insufficient available space for a large request, then it is queued up behind other existing requests. When space does become available, all requests are considered in the order in which they were originally made. If there is sufficient space for a given request, then that request is allowed to continue and the next request is considered. If there is insufficient space for a given request, then that request is skipped and the next request is considered." ::= { jmsServerEntry 80 }
jmsServerBlockingSendPolicy OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Determines whether the JMS server delivers smaller messages before larger ones when a destination has exceeded its maximum number of messages. FIFO prevents the JMS server from delivering smaller messages when larger ones are already waiting for space. Preemptive allows smaller send requests to preempt previous larger ones when there is sufficient space for smaller messages on the destination. This policy is defined only for the JMS server; it cannot be set on individual destinations. Additional information on the FIFO and Preemptive policies is provided below. FIFO (first in, first out) indicates that all send requests for the same destination are queued up one behind the other until space is available. No send request is permitted to successfully complete if there is another send request waiting for space before it. When space is limited, the FIFO policy prevents the starvation of larger requests because smaller requests cannot continuously use the remaining available space. Smaller requests are delayed, though not starved, until the larger request can be completed. When space does become available, requests are considered in the order in which they were made. If there is sufficient space for a given request, then that request is completed and the next request is considered. If there is insufficient space for a given request, then no further requests are considered until sufficient space becomes available for the current request to complete. Preemptive indicates that a send operation can preempt other blocking send operations if space is available. That is, if there is sufficient space for the current request, then that space is used even if there are other requests waiting for space. When space is limited, the Preemptive policy can result in the starvation of larger requests. For example, if there is insufficient available space for a large request, then it is queued up behind other existing requests. When space does become available, all requests are considered in the order in which they were originally made. If there is sufficient space for a given request, then that request is allowed to continue and the next request is considered. If there is insufficient space for a given request, then that request is skipped and the next request is considered." ::= { jmsServerEntry 80 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.140.625.660.1.1 | jmsServerIndex | 0 | 0 | Unique value directed from ObjectName which is used as table index |
| 1.3.6.1.4.1.140.625.660.1.5 | jmsServerObjectName | 0 | 0 | JMX-standard MBean name |
| 1.3.6.1.4.1.140.625.660.1.10 | jmsServerType | 0 | 0 | BEA-proprietary MBean type |
| 1.3.6.1.4.1.140.625.660.1.15 | jmsServerName | 0 | 0 | BEA-proprietary MBean name |
| 1.3.6.1.4.1.140.625.660.1.20 | jmsServerParent | 0 | 0 | BEA-proprietary Parent object's identification, with syntax |
| 1.3.6.1.4.1.140.625.660.1.25 | jmsServerTargets | 0 | 0 | Targets on which this deployment is deployed. |
| 1.3.6.1.4.1.140.625.660.1.30 | jmsServerSessionPools | 0 | 0 | Get all the session pools defined for the JMS Server. |
| 1.3.6.1.4.1.140.625.660.1.35 | jmsServerDestinations | 0 | 0 | A map containing all defined destinations and their associated JNDI names. |
| 1.3.6.1.4.1.140.625.660.1.40 | jmsServerStore | 0 | 0 | Get the backing store for the JMS server. |
| 1.3.6.1.4.1.140.625.660.1.45 | jmsServerBytesMaximum | 0 | 0 | The value of bytesMaximum. This is the maximum number of bytes that can be stored in the JMS Server at any one time. |
| 1.3.6.1.4.1.140.625.660.1.50 | jmsServerBytesThresholdHigh | 0 | 0 | The value of bytesThresholdHigh. If there is no threshold condition and the number of bytes stored in the JMS Server exc… |
| 1.3.6.1.4.1.140.625.660.1.55 | jmsServerBytesThresholdLow | 0 | 0 | The value of bytesThresholdLow. If there is a threshold condition and the number of bytes stored in the JMS Server drops bel… |
| 1.3.6.1.4.1.140.625.660.1.60 | jmsServerMessagesMaximum | 0 | 0 | The value of messagesMaximum. This is the maximum number of messages that can be stored in the JMS Server at any one time.… |
| 1.3.6.1.4.1.140.625.660.1.65 | jmsServerMessagesThresholdHigh | 0 | 0 | The value of messagesThresholdHigh. If there is no threshold condition and the number of messages stored in the JMS Server exce… |
| 1.3.6.1.4.1.140.625.660.1.70 | jmsServerMessagesThresholdLow | 0 | 0 | The value of messagesThresholdLow. If there is a threshold condition and the nubmer of messages stored in the JMS Server d… |
| 1.3.6.1.4.1.140.625.660.1.71 | jmsServerInsertionPausedAtStartup | 0 | 0 | Indicates whether insertion is paused at startup on destinations targeted to this JMS server. A destination cannot receive any … |
| 1.3.6.1.4.1.140.625.660.1.72 | jmsServerStoreEnabled | 0 | 0 | Specifies whether message persistence is supported for this JMS server. When set to true, the default, then if the JMS server … |
| 1.3.6.1.4.1.140.625.660.1.73 | jmsServerAllowsPersistentDowngrade | 0 | 0 | Specifies whether JMS clients will get an exception when sending persistent messages to a destination targeted to a JMS server … |
| 1.3.6.1.4.1.140.625.660.1.74 | jmsServerExpirationScanInterval | 0 | 0 | The number of seconds between this JMS server's cycles of scanning local destinations for expired messages. A value of 0 disabl… |
| 1.3.6.1.4.1.140.625.660.1.75 | jmsServerProductionPausedAtStartup | 0 | 0 | Specifies whether production is paused at server startup on destinations targeted to this JMS server. A destination cannot rece… |
| 1.3.6.1.4.1.140.625.660.1.76 | jmsServerTemporaryTemplateName | 0 | 0 | The name of a configured JMS template that this JMS server uses to create temporary destinations. Entering a template name, re… |
| 1.3.6.1.4.1.140.625.660.1.77 | jmsServerMaximumMessageSize | 0 | 0 | The maximum number of bytes allowed in individual messages on this JMS server. The size of a message includes the message body,… |
| 1.3.6.1.4.1.140.625.660.1.78 | jmsServerDeploymentOrder | 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.660.1.79 | jmsServerMessageBufferSize | 0 | 0 | The amount of memory (in bytes) that this JMS server can use to store message bodies before it writes them to disk. When the JM… |
| 1.3.6.1.4.1.140.625.660.1.81 | jmsServerHostingTemporaryDestinations | 0 | 0 | Specifies whether this JMS server can be used to host temporary destinations. If this field is enabled and no Temporary Templa… |
| 1.3.6.1.4.1.140.625.660.1.82 | jmsServerPagingDirectory | 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.660.1.83 | jmsServerTemporaryTemplateResource | 0 | 0 | The name of a JMS module that contains a template that this JMS server can use to create temporary destinations. Entering a JM… |
| 1.3.6.1.4.1.140.625.660.1.84 | jmsServerConsumptionPausedAtStartup | 0 | 0 | Indicates whether consumption is paused at startup on destinations targeted to this JMS server at startup. A destination cannot… |