- Click to expand the JMS node.
- Click the JMS Connection Factories node. The JMS Connection Factories table
displays in the right pane showing all the connection factories defined in your
domain.
- Click the Create a new JMS Connection Factory text link. A dialog displays in
the right pane showing the tabs associated with configuring a new connection
factory.
- Enter values in the attribute fields.
- Click Create to create a connection factory instance with the name you specified
in the Name field. The new instance is added under the JMS Connection
Factories node in the left pane.
- Assign the JMS Connection Factory to a WebLogic Server.
- Click to expand the JMS node.
- Click the JMS Connection Factories node. The JMS Connection Factories table
displays in the right pane showing all the connection factories defined in your
domain.
- Click the Clone icon in the row of the connection factory you want to clone. A
dialog displays in the right pane showing the tabs associated with cloning a
connection factory.
- Enter values in the attribute fields.
- Click Create to create a connection factory instance with the name you specified
in the Name field. The new instance is added under the JMS Connection
Factories node in the left pane.
- Assign the JMS Connection Factory to a WebLogic Server.
Attribute
|
Description
|
Range of Values
|
Default Value
|
Name
|
Name of the connection factory. The JNDI name is configured separately.
This attribute is not dynamically configurable.
|
Java identifier, unique within specific cluster
|
My JMS Connection Factory[-n]
|
JNDI Name
|
Name that is assigned to and used to look up the connection factory within the JNDI namespace. The connection factory name is configured separately.
This attribute is not dynamically configurable.
|
Java identifier, unique within JNDI namespace
|
null
|
Client ID
|
Client ID that can be used for clients with durable subscribers. For more information about durable subscribers, see Programming WebLogic JMS.
This attribute is not dynamically configurable.
|
Java identifier
|
null
|
Default Priority
|
Default priority used for messages for which a priority is not explicitly defined.
For information about defining the priority when sending messages, see Programming WebLogic JMS.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
0 through 9
|
4
|
Default Time to Live
|
Default maximum length of time (in milliseconds) that a message will exist. Used for messages for which a priority was not explicitly defined. A value of 0 indicates that the message has an infinite amount time to live.
For information about defining the time-to-live when sending messages, see Programming WebLogic JMS.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
0 through 263-1
|
0
|
Default Delivery Mode
|
Default delivery mode used for messages for which a delivery mode is not explicitly defined.
For more information about delivery modes and defining them when sending messages, see Programming Weblogic JMS.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
Persistent or Non-Persistent
|
Persistent
|
Messages Maximum
|
Maximum number of messages that may exist for an asynchronous session and that have not yet been passed to the message listener.
A value of -1 indicates that there is no limit on the number of messages. In this case, however, the limit is set to the amount of remaining virtual memory.
When the number of messages reaches the Messages Maximum value:
For multicast sessions, new messages are discarded according the policy specified by the Overrun Policy attribute and a DataOverrunException is thrown.
For non-multicast sessions, new messages are flow-controlled, or retained on the server until the application can accommodate the messages.
For multicast sessions, when a connection is stopped, messages will continue to be delivered, but only until the Messages Maximum value is reached. Once this value is reached, messages will be discarded based on the Overrun policy.
For more information about asynchronous messages and multicasting, see Programming WebLogic JMS.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
-1, 1 through 231-1
|
10
|
Overrun Policy
|
Overrun policy for multicast sessions. When the number of outstanding messages reaches the Messages Maximum attribute value, messages are discarded based on the specified policy. If set to KeepNew, the most recent messages are given priority over the oldest messages, and the oldest messages are discarded, as needed. If set to KeepOld, the oldest messages are given priority over the most recent messages, and the most recent messages are discarded, as needed.
Message age is defined by the order of receipt, not by the JMSTimestamp value.
For more information about asynchronous messages and multicasting, see Programming WebLogic JMS.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
KeepNew, KeepOld
|
KeepOld
|
Allow Close In OnMessage
|
Flag for specifying whether or not a connection factory creates message consumers that allow a close() method to be issued within its onMessage() method call. If selected, a close() method call from within an onMessage() method call will succeed instead of blocking forever. If the acknowledge mode of the session is set to AUTO_ACKNOWLEDGE, the current message will still be acknowledged automatically when the onMessage() call completes.
The onMessage() method is implemented to support asynchronous message delivery as described in Programming WebLogic JMS.
|
Boolean
Enabled = selected
Disabled = not selected
|
Not Selected
|
Attribute
|
Description
|
Range of Values
|
Default Value
|
Transaction Timeout
|
Timeout value (in seconds) for transacted sessions. If a transacted session is still active after the timeout has elapsed, the transaction is rolled back. A value of 0 indicates that the default value will be used.
If you have long-running transactions, you might want to adjust the value of this attribute to allow transactions to complete.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
0 through 232-1
|
3600
|
User Transactions Enabled
|
Flag for specifying whether or not a connection factory creates sessions that are JTA aware. If set, the associated message producers and message consumers look into the running thread for a transaction context. Otherwise, the current JTA transaction will be ignored.
This attribute is dynamically configurable, but changes will only affect new connections; existing connections will not be impacted.
|
Boolean
Enabled = selected
Disabled = not selected
|
Not Selected
|