Skip navigation.

WebLogic Server Configuration Reference

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader




This class represents a JMS distributed queue, which is comprised of multiple physical JMS queues as members of a single distributed set of queues that can be served by multiple WebLogic Server instances within a cluster.



ForwardDelay="number of seconds"
LoadBalancingPolicy=( "Round-Robin" | "Random" )
Targets="list of Target names"
Template="JMSTemplate name"


Parent Elements


Child Elements



Table 29-1 JMSDistributedQueue attributes



Range of Values and Default


A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.

Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.

Default: 1000

Minimum: 0

Maximum: 231-1


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

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

Admin Console field label: Forward Delay

Units: seconds

Default: -1


The JNDI name used to look up a virtual destination within the JNDI namespace. 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.

Admin Console field label: JNDI Name

Required: no


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

  • Round-Robin - The system maintains an ordering of physical destinations within the distributed set by distributing the messaging load across the physical 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 physical members in the distributed set, then those members appear multiple times in the ordering.

  • Random - The weight assigned to the physical destinations is used to compute a weighted distribution for the physical members of the distributed set. The messaging load is distributed across the physical 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.

Admin Console field label: Load Balancing Policy

Required: no

Default: Round-Robin


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

Admin Console field label: Name

Required: no


Optional information that you can include to describe this configuration.

Admin Console field label: Notes

Required: no


The targets in the current domain on which this item can be deployed.

Required: no


The JMS template that the distributed destination is derived from.

Required: no


Skip navigation bar  Back to Top Previous Next