Skip navigation.

Administration Console Online Help

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index

 


JMS Distributed Queue --> Configuration --> General

Tasks     Related Topics     Attributes

Overview

This tab defines general configuration attributes for a set of JMS distributed queues.

Tasks

Creating a Distributed Queue and Creating Members Automatically

Creating a Distributed Queue and Adding Existing Physical Queues as Members Manually

Related Topics

"Developing a WebLogic JMS Application" in Programming WebLogic JMS

Attributes

Table 8-1

Attribute Label

Description

Value Constraints

Name

The name of this distributed queue configuration. WebLogic Server uses an MBean to implement and persist the configuration.

MBean: weblogic.management.
configuration.
JMSDistributedQueueMBean

Attribute: Name


JNDI Name

The JNDI name used to look up the distributed queue within the JNDI namespace. Applications can use the JNDI name to look up the distributed queue. If not specified, then the distributed queue is not bound into the JNDI namespace.

MBean: weblogic.management.
configuration.
JMSDistributedQueueMBean

Attribute: JNDIName


Load Balancing Policy

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. Valid values are:

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

  • Random - The weight assigned to distributed queue members during configuration is used to compute a weighted distribution for the underlying physical queues in the distributed set. The messaging load is distributed across the queue 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.

MBean: weblogic.management.
configuration.
JMSDistributedQueueMBean

Attribute: LoadBalancingPolicy

Default: Round-Robin

Valid values:

  • Round-Robin

  • Random

Dynamic: yes

Forward Delay (seconds)

The amount of time, in seconds, that a distributed queue member with messages, but which has no consumers, will wait before forwarding its messages to other queue members that do have consumers.

A value of -1 indicates that no messages are forwarded to other queue members.

MBean: weblogic.management.
configuration.
JMSDistributedQueueMBean

Attribute: ForwardDelay

Default: -1

 

Skip navigation bar  Back to Top Previous Next