DistributedQueueBean

Overview

A distributed queue is one that can be load-balanced across a cluster.

Deprecated. 10.3.4.0, since Weighted Distributed Destination has been deprecated and replaced by Uniform Distributed Destination

Related MBeans

This section describes attributes that provide access to other MBeans.

DistributedQueueMembers

The list of all queue members that make up the aggregate distributed queue.

The name of the specific queue and any configuration information about that queue (such as its relative weight) can be configured in the distributed queue member.

Attributes

This section describes the following attributes:

ForwardDelay

The number of seconds after which a distributed queue member with no consumers will wait before forwarding its messages to other distributed queue members that do have consumers.

The default value of -1 disables this feature so that no messages are forwarded to other distributed queue members.

Id

Return the unique identifier of this bean instance.

JNDIName

The name used to bind a virtual destination to the JNDI tree. Applications can use the JNDI name to look up the virtual destination.

If not specified, then the destination is not bound into the JNDI namespace.

LoadBalancingPolicy

Determines the load balancing policy for producers sending messages to a distributed destination in order to balance the message load across the members of the distributed set.

• Round-Robin

  - The system maintains an ordering of physical topic members within the set by distributing the messaging load across the topic members one at a time in the order that they are defined in the configuration file. Each WebLogic Server maintains an identical ordering, but may be at a different point within the ordering. If weights are assigned to any of the topic members in the set, then those members appear multiple times in the ordering.

• Random

  - The weight assigned to the topic members is used to compute a weighted distribution for the members of the set. The messaging load is distributed across the topic members by pseudo-randomly accessing the distribution. In the short run, the load will not be directly proportional to the weight. In the long run, the distribution will approach the limit of the distribution. A pure random distribution can be achieved by setting all the weights to the same value, which is typically set to 1.

Name

The name of this entity, represented in XML as an attribute.

Many of the elements within the JMS module are named entities. All of the named entities encased by a type in the XML file must be unique. This is the identifier used to delineate a particular entity within the JMS module.

This attribute cannot be modified externally from the module (for example, with a deployment plan) because it may be used inside the module referentially.

Notes

Optional information that you can include to describe this named JMS descriptor bean.

JMS module saves this note in the JMS descriptor file as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved.

Note:

If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

ResetDeliveryCountOnForward

Determines whether or not the delivery count is reset during message forwarding between distributed queue members.

The default value of true resets the delivery counts on messages when they are forwarded to another distributed queue member.

SAFExportPolicy

The SAF Export Policy controls which applications can send JMS messages to this destination through Store-and-Forward.

• All

  - This destination allows everyone to send JMS messages to it through SAF.

• None

  - This destination does not allow anyone to send JMS messages from a remote server to it through SAF.

This attribute is dynamically configurable. A dynamic change of this attribute will affect only messages sent after the update has been made.

UnitOfOrderRouting

Gets the "unit-of-order-routing" element.

A WLMessageProducer with Unit of Order uses the "unit-of-order-routing" element rather than the "load-balancing-policy" criteria to select the Distributed Destination Member.

Unit of Order may have been set programmatically with WLProducer, or administratively on the ConnectionFactory or Destination.

• Hash

  - producers will compute the Distributed Destination Member from the hash code of the Unit of Order.

• PathService

  - the configured Path Service will determine the Distributed Destination Member.

Operations

This section describes the following operations:

isSet

Return true if the given property has been explicitly set in this bean.

unSet

Restore the given property to its default value.