Table 42-1 JMSTopicMBean Element Attributes
Attribute
|
Description
|
Range of Values and Default
|
Console Label
|
Bytes-Maximum
|
The value of BytesMaximum.
The maximum number of bytes that may be stored in the destination. A value of -1 specifies that there is no limit on the number of bytes that can be stored in the destination.
Range of Values: >= BytesThresholdHigh
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Bytes Maximum
|
Bytes-Paging-Enabled
|
Return one of "true", "false", or "default".
Flag for specifying whether or not bytes paging is enabled on the destination:
If this flag is not selected (true), a paging store has been configured for the JMS Server, and both the BytesThresholdLow and BytesThresholdHigh attribute values are greater than -1, then bytes paging is enabled for this destination.
If this attribute is set to "default", then this value inherits the JMS template's value--if a JMS template is specified. If no template is configured for the destination, then the Default value is equivalent to False.
|
Default: default
Valid values:
|
Bytes Paging Enabled
|
Bytes-Threshold-High
|
The value of BytesThresholdHigh.
Upper threshold value that triggers events based on the number of bytes stored in the destination. If the number of bytes exceeds this threshold, the triggered events are:
Log Messages - message is logged on the server indicating a high threshold condition.
Bytes Paging - bytes paging is enabled (and a paging store has been configured), then destination-level bytes paging is started.
Flow Control - flow control is enabled, the destination becomes armed and instructs producers to begin decreasing their message flow.
A value of -1 specifies that bytes paging, flow control, and threshold log messages are disabled for the destination.
Range of Values:<= BytesMaximum; >BytesThresholdLow
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
Note:Bytes paging cannot be dynamically disabled by resetting the BytesThresholdHigh to -1. To disable paging, you could set the BytesThresholdHigh to a very large number, so that paging would not be triggered.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Bytes Threshold High
|
Bytes-Threshold-Low
|
The value of BytesThresholdLow.
Lower threshold value that triggers events based on the number of bytes stored in the destination. If the number of bytes falls below this threshold, the triggered events are:
Log Messages - message is logged on the server indicating that the threshold condition has cleared.
Bytes Paging - bytes paging is enabled, paging is stopped (if paging is occurring).
Flow Control - flow control is enabled, the destination becomes disarmed and instructs producers to begin increasing their message flow.
A value of -1 specifies that bytes paging, flow control, and threshold log messages are disabled for the destination.
Range of Values: < BytesThresholdHigh
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Bytes Threshold Low
|
Delivery-Mode-Override
|
The DeliveryModeOverride value.
The delivery mode assigned to all messages that arrive at the destination regardless of the DeliveryMode specified by the message producer.
A value of No-Delivery specifies that the DeliveryMode will not be overridden.
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: No-Delivery
Valid values:
|
Delivery Mode Override
|
Destination-Keys
|
Return a read-only array of the destination keys of the template or destination.
|
|
Destination Keys
|
Error-Destination
|
The ErrorDestination value for messages that have reached their redelivery limit.
Defines the name of the target destination for messages that have reached their redelivery limit. If no error destination is configured, then such messages are simply dropped.
Note: The error destination must be a destination that is configured on the local JMS server.
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: null
Minimum: -1
|
Error Destination
|
JNDIName
|
The JNDI name of the destination.
This value is the name used to look up the destination within the JNDI namespace. If not specified, the destination name is not advertised through the JNDI namespace and cannot be looked up and used.
This attribute is not dynamically configurable.
|
|
JNDIName
|
JNDIName-Replicated
|
If JNDINameReplicated is set to true, then the JNDI name for the destination (if present) is replicated across the cluster. If JNDINameReplicated is set to false, then the JNDI name for the destination (if present) is only visible from the server of which this destination is a part.
|
Default: true
|
JNDIName Replicated
|
Messages-Maximum
|
The value of MessagesMaximum.
The maximum number of messages that may be stored in the destination. A value of -1 specifies that there is no limit on the number of messages that can be stored in the destination.
Range of Values: >= MessagesThresholdHigh
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Messages Maximum
|
Messages-Paging-Enabled
|
Return one of "true", "false", or "default".
Flag for specifying whether or not messages paging is enabled on the destination:
If this flag is not selected (true), a paging store has been configured for the JMS Server, and both the MessagesThresholdLow and MessagesThresholdHigh attribute values are greater than -1, then messages paging is enabled for this destination.
If this attribute is set to "default", then this value inherits the JMS template's value--if a JMS template is specified. If no template is configured for the destination, then the Default value is equivalent to False.
|
Default: default
Valid values:
|
Messages Paging Enabled
|
Messages-Threshold-High
|
The value of MessagesThresholdHigh.
Upper threshold value that triggers events based on the number of messages stored in the destination. If the number of messages exceeds this threshold, the triggered events are:
Log Messages - message is logged on the server indicating a high threshold condition.
Bytes Paging - messages paging is enabled (and a paging store has been configured), then destination-level messages paging is started.
Flow Control - flow control is enabled, the destination becomes armed and instructs producers to begin decreasing their message flow.
A value of -1 specifies that messages paging, flow control, and threshold log messages are disabled for the destination.
Range of Values:<= MessagesMaximum; >MessagesThresholdLow
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
Note:Messages paging cannot be dynamically disabled by resetting the BytesThresholdHigh to -1. To disable paging, you could set the BytesThresholdHigh to a very large number, so that paging would not be triggered.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Messages Threshold High
|
Messages-Threshold-Low
|
The value of MessagesThresholdLow.
Lower threshold value that triggers events based on the number of messages stored in the destination. If the number of messages falls below this threshold, the triggered events are:
Log Messages - message is logged on the server indicating that the threshold condition has cleared.
Bytes Paging - messages paging is enabled, paging is stopped (if paging is occurring).
Flow Control - flow control is enabled, the destination becomes disarmed and instructs producers to begin increasing their message flow.
A value of -1 specifies that messages paging, flow control, and threshold log messages are disabled for the destination.
Range of Values: < MessagesThresholdHigh
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Messages Threshold Low
|
Multicast-Address
|
The multicast address used by the destination.
The IP address used for multicasting. This address is used to transmit messages to multicast consumers.
|
|
Multicast Address
|
Multicast-Port
|
The multicast port for the destination.
This is the IP port used for multicasting. This port is used to transmit messages to multicast consumers.
|
Default: 6001
Minimum: 1
Maximum: 65535
|
Multicast Port
|
Multicast-TTL
|
The number of network hops that a multicast message is allowed to travel.
This is the Time-To-Live value used for multicasting, which specifyies the number of routers that the message can traverse enroute to the consumers. A value of 1 indicates that the message will not traverse any routers and is limited to one subnet. This value is independent of the JMSExpirationTime value.
|
Default: 1
Minimum: 0
Maximum: 255
|
Multicast TTL
|
Name
|
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.
|
|
Name
|
Notes
|
Optional information that you can include to describe this configuration.
|
|
Notes
|
Priority-Override
|
The PriorityOverride value.
This value is the priority assigned to all messages that arrive at the destination, regardless of the Priority specified by the message producer.
The default value (-1) specifies that the destination will not override the Priority setting.
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: weblogic.management.configuration.JMSConstants.PRIORITY_MAXIMUM
|
Priority Override
|
Redelivery-Delay-Override
|
The RedeliveryDelayOverride value in milliseconds before rolled back and recovered messages are redelivered.
Defines the delay, in milliseconds, before rolled back or recovered messages are redelivered, regardless of the RedeliveryDelay specified by the consumer and/or connection factory.
The default value (-1) specifies that the destination will not override the RedeliveryDelay setting.
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Redelivery Delay Override
|
Redelivery-Limit
|
The number of redelivery tries a message can have before it is placed in the error destination.
Depending on whether an error destination is configured, the following occurs when the redelivery limit is reached:
If an error destination is configured and the error destination is at quota, then an error message is logged and the message is dropped. However, if the message is persistent, it remains in the persistent store. This ensures that a persistent message will be redelivered when WebLogic Server is rebooted.
The default value (-1) specifies that the destination will not override the RedeliveryLimit setting.
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
Note:Changing the RedeliveryLimit does not affect messages that have already reached this limit. The next time such messages are redelivered, they will immediately be redirected to the error destination. The number of times of message has been redelivered is not persisted. This means that after a restart the number of delivery attempts on each message is reset to zero.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Redelivery Limit
|
Store-Enabled
|
Return one of "true", "false", or "default".
Flag specifying whether or not the destination uses the persistent store specified by the JMS server:
This attribute is not dynamically configurable.
|
Default: default
Valid values:
|
Store Enabled
|
Template
|
The JMS template from which the destination is derived.
If this attribute is not defined, then the attributes for the destination must be specified as part of the destination. The Template attribute setting per destination is static. The template attributes, however, can be modified dynamically.
Note:Attributes that are set to their default values will inherit their destination values from the JMS template at run time. If this attribute is not defined, then the attributes for the destination must be specified as part of the destination.
|
|
Template
|
Time-To-Deliver-Override
|
The TimeToDeliver override value either in milliseconds or as a schedule.
Defines the default delay, in milliseconds, between when a message is produced and when it is made visible on its target destination, regardless of the delivery time specified by the producer and/or connection factory.
The default value (-1) specifies that the destination will not override the TimeToDeliver setting. The TimeToDeliverOverride can be specified either as a long or as a schedule.
Note:Changing the TimeToDeliverOverride only affects future message delivery, it does not affect message delivery of already produced messages.
|
Default: "-1"
|
Time To Deliver Override
|
Time-To-Live-Override
|
The TimeToLiveOverride value.
Defines the TimeToLive value assigned to all messages that arrive at the destination, regardless of the TimeToLive specified by the message producer.
The default value (-1) specifies that the destination will not override the TimeToLive setting.
This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.
|
Default: -1
Minimum: -1
Maximum: 9223372036854775807
|
Time To Live Override
|