JMS Topic --> Configuration --> Overrides
Tasks Related Topics Attributes
Overview
This tab defines override configuration attributes for a topic destination. After defining a JMS server, you can configure its topics. You can configure one or more topics for each JMS server.
Note: You configure destinations explicitly or by configuring a JMS template that can be used to define multiple destinations with similar attribute settings, as described in JMS Template Tasks.
Tasks
Related Topics
WebLogic JMS Fundamentals in Programming WebLogic JMS
Managing WebLogic JMS in Programming WebLogic JMS
Developing a WebLogic JMS Applicationin Programming WebLogic JMS
Attributes
|
Attribute Label |
Description |
Value Constraints |
|---|---|---|
| Priority Override |
The priority assigned to all messages that arrive at the destination, regardless of the Priority specified by the message producer. If no JMS template is specified for this destination, then -1 means that the destination will not override the Priority setting. Otherwise, -1 means that the value comes from the template.This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management.
configuration. JMSTopicMBeanAttribute: PriorityOverride | Minimum: -1Maximum: 9Default: -1Dynamic: yes |
| Time To Live Override |
The time-to-live value assigned to all messages that arrive at the destination, regardless of the TimeToLive specified by the message producer. If no JMS template is specified for this destination, then -1 means that the destination will not override the TimeToLive setting. Otherwise, -1 means that the value comes from the template.This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management.
configuration. JMSTopicMBeanAttribute: TimeToLiveOverride | Minimum: -1Maximum: 9223372036854775807Default: -1Dynamic: yes |
| Time To Deliver Override |
The default delay, either in milliseconds or as a schedule, 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. If no JMS template is specified for this destination, then -1 means that the destination will not override the TimeToDeliver setting. Otherwise, -1 means that the value comes from the template.The Time To Deliver Override can be specified either as a long or as an advanced scheduling syntax (see "Setting Message Delivery Times" in Programming JMS for details.)Note: Changing the Time To Deliver Override only affects future message delivery, it does not affect message delivery of already produced messages. MBean: weblogic.management.
configuration. JMSTopicMBeanAttribute: TimeToDeliverOverride | Default: "-1"Dynamic: yes |
| Delivery Mode Override |
The delivery mode assigned to all messages that arrive at the destination regardless of the DeliveryMode specified by the message producer. If no JMS template is specified for this destination, then No-Delivery means the DeliveryMode will not be overridden. Otherwise, No-Delivery means that the value comes from the template.This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted.MBean: weblogic.management.
configuration. JMSTopicMBeanAttribute: DeliveryModeOverride |
Default: No-DeliveryValid values:
|
|
|
|