Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS Connection Factory

Column Display Related Tasks Related Topics

Connection factories are used to create connections for JMS clients. A connection factory supports concurrent use, enabling multiple threads to access it simultaneously. You can configure one or more connection factories to create connections with predefined parameters for the connections returned to JMS, such as specifying a default priority to use for messages when a priority is not explicitly defined on the message.

This page summarizes the JMS connection factories that have been created for this JMS module.

#### Column Display

You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

The following table lists all of the data points that you can display in columns on this page.

Name | Description
--- | ---
Name | The name of this JMS connection factory.
JNDI Name | 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. MBean Attribute (Does not apply to application modules): `JMSConnectionFactoryBean.JNDIName`
Client ID | MBean Attribute: `JMSConnectionFactoryMBean.ClientID` Changes take effect after you redeploy the module or restart the server.
Default Priority |
Default Time-to-Live |
Default Redelivery Delay |
Acknowledge Policy |
Allow Close In On Message |
Default Delivery Mode | The delivery mode assigned to all messages sent by a producer using this connection factory. Message producers can get the delivery mode explicitly by calling the `javax.jms.MessageProducer.getDeliveryMode()` method. Note: This value is dynamic. It 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. MBean Attribute: `JMSConnectionFactoryMBean.DefaultDeliveryMode`
Default Time To Deliver | The number of milliseconds between when a message is produced and when it is made visible on its target destination. Message producers can get the time-to-deliver explicitly by calling the `weblogic.jms.extensions.WLMessageProducer.getTimeToDeliver()` method. Range of Values: Between `0` and a positive 64-bit integer. Note: This value is dynamic. It 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. MBean Attribute: `JMSConnectionFactoryMBean.DefaultTimeToDeliver` Minimum value: `0` Maximum value: `9223372036854775807`
Messages Maximum | The 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. This value is dynamic. It 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 topic subscribers that use the multicast extension, also see the Overrun Policy field.) When the number of messages reaches the MessagesMaximum value: For multicast sessions, new messages are discarded according the policy specified by the OverrunPolicy value 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. Range of Values: Between -1 and a positive 32-bit integer. Note: For multicast sessions, when a connection is stopped, messages will continue to be delivered, but only until the MessagesMaximum value is reached. Once this value is reached, messages will be discarded based on the Overrun policy. MBean Attribute: `JMSConnectionFactoryMBean.MessagesMaximum` Minimum value: `-1` Maximum value: `2147483647`
Overrun Policy | Overrun policy for topic subscribers that use the multicast extension. The policy to use when the number of outstanding multicast messages reaches the value specified in the Messages Maximum field and some messages must be discarded. `Keep New` indicates that the most recent messages are given priority over the oldest messages, and the oldest messages are discarded, as needed. `Keep Old` indicates that 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. The policy to use when the number of outstanding multicast messages reaches the value specified in MessagesMaximum and some messages must be discarded. If set to `Keep New`, the most recent messages are given priority over the oldest messages, and the oldest messages are discarded, as needed. If set to `Keep Old`, 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. Note: This value is dynamic. It 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. MBean Attribute: `JMSConnectionFactoryMBean.OverrunPolicy`
Transaction Timeout |
XA Connection Factory Enabled |

Related Tasks

- Configure connection factories

Related Topics

- Configuring and Managing WebLogic JMS
- Programming WebLogic JMS