Technical data

Configuring JMS
Administration Guide 17-9
l Maximum number of outstanding messages that may exist for an
asynchronous session and the overrun policy (that is, the action to be taken,
for multicast sessions, when this maximum is reached).
l Whether or not the close() method is allowed to be called from the
onMessage() method.
l Whether all messages or only previously received messages are
acknowledged.
JMS connection factories must be uniquely named within a domain. For more
information, see “JMS Configuration Naming Rules” on page 17-3.
n Transaction attributes—transaction time-out, whether or not Java Transaction
API (JTA) user transactions are allowed, and whether or not a transaction (XA)
queue or XA topic connection factory is returned.
n Targets (WebLogic Server instances) that are associated with a connection
factory to support clustering. Targets enable you to limit the set of servers,
groups, and/or clusters on which a connection factory may be deployed.
WebLogic JMS defines one connection factory, by default:
weblogic.jms.ConnectionFactory. All configuration attributes are set to their
default values for this default connection factory. If the default connection factory
definition is appropriate for your application, you do not need to configure any
additional connection factories for your application.
Note: Using the default connection factory, you have no control over the JMS server
on which the connection factory may be deployed. If you would like to target
a particular JMS server, create a new connection factory and specify the
appropriate JMS server target(s).
For instructions on creating and configuring a connection factory, see “JMS
Connection Factories” in the Administration Console Online Help.
Some connection factory attributes are dynamically configurable. When dynamic
attributes are modified at run time, the new values become effective for new
connections only, and do not affect the behavior of existing connections.