The load-balancing parameters allow client to choose how they wish to distribute the work to the configured servers.
|Security roles||The following roles have read, write, and invoke permission for all non-encrypted attributes and operations in this MBean:
|Fully Qualified Interface Name||If you use the
|Factory Methods||No factory methods. Instances of this MBean are created automatically.|
You can access this MBean from the following MBean attributes:
This section describes the following attributes:
Specifies whether non-anonymous producers created through a connection factory are load balanced within a distributed destination on a per-call basis.
If enabled, the associated message producers are load balanced
If disabled, the associated message producers are load balanced
on the first
Producer Load Balancing Policy restricts where
a JMS Message Producer can load balance its messages among members
of a distributed destination (DD).
The valid values are:
- The default value. All running members are candidates.
- Only one member per JVM is a candidate.
Unit of Order and Unit of Work messages are not affected by this setting.
If every WebLogic Server JVM is running a single member of the
There can be at most one
Per-JVM candidate member
of a particular DD per WebLogic Server JVM.
Per-JVM load balance candidates will either be
(a) members of a DD hosted on a cluster targeted JMS Server or SAF
Agent that are running on their preferred server (for example,
members that have not failed over or migrated), OR (b) the
lexicographically least member name on the same JVM where the DD
member is not hosted on a cluster targeted JMS Server or SAF Agent.
A member in (a) takes precedence over a member in (b). If two
members satisfy (a), then the lexicographically least member name
If the DD is a
Replicated Distributed Topic or if
Load Balance Enabled is set to
then MessageProducers are 'pinned' to a single member and therefore
only load balance on initial creation or after a failure. If a
MessageProducer is already pinned to a particular DD member on a
particular JVM, and the DD is not hosted on JMS Servers or SAF
Agents that are targeted to a cluster, and a new member of the DD
starts on the same JVM, then the MessageProducer's future messages
stay pinned to its original member regardless of whether the member
is still a
Per-JVM load balance candidate.
You can override the
Producer Load Balancing Policy
on a custom Connection Factory by specifying the system properties
every WebLogic Server in a cluster (the latter property takes
precedence over the former). If a Connection Factory is overridden
by one of these system properties, then the host WebLogic Server
will log an Info message BEA-040538 with the name of the Connection
Factory, the system property, and the system property value once
the first MessageProducer uses the connection factory.
For a similar setting that controls the load balancing of messages forwarded Exactly-Once via a Store-and-Forward Agent (SAF Agent), see the Exactly Once Load Balancing Policy attribute on a SAF Imported Destinations bean.
This attribute is dynamic and can be changed at any time. However, changing the value does not affect existing connections. It only affects new connections made with this connection factory.
For more information, see:
Specifies whether a server instance that is load balancing consumers or producers across multiple members destinations of a distributed destination, will first attempt to load balance across any other physical destinations that are also running on the same server instance.
This section describes the following operations:
Return true if the given property has been explicitly set in this bean.
Restore the given property to its default value.