Several parameters concerning how the JMS server should behave
with regard to their clients can be configured with the client
parameters bean. For example, the client-id a client should have
when using this connection factory can be configured with a client
parameter bean.

Factory Methods

No explicit creator method. The child shares the lifecycle of its parent.

Many clients producing messages can cause the server to fall
behind in processing messages. The flow control parameters can help
by slowing down production of messages. Using flow control can help
the overall throughput of the system.

Factory Methods

No explicit creator method. The child shares the lifecycle of its parent.

The global JNDI name used to look up a connection factory within
a clustered JNDI namespace.

In a clustered environment, this name is propagated to the
entire cluster. If you want the JNDI name to be bound only on the
local server, and not propagated to the rest of the cluster, then
use the Local JNDI Name setting.

If not specified, then the connection factory is not bound into
a clustered JNDI namespace.

The local JNDI name used to look up the connection factory
within the JNDI namespace of the server where the connection
factory is targeted. In a clustered environment, this name is bound
only on the local server instance and is not propagated to the rest
of the cluster.

If not specified, then the connection factory is not bound into
the local JNDI namespace.