This tab defines transaction configuration attributes for a JMS connection factory. After defining a JMS server, you can configure one or more connection factories to create connections with predefined attributes.

Attribute Label	Description	Value Constraints
Transaction Timeout	All transactions on connections created with this connection factory will have this timeout value expressed in seconds. 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. MBean: weblogic.management. configuration. JMSConnectionFactoryMBean Attribute: TransactionTimeout	Minimum: 0 Maximum: 2147483647 Default: 3600 Configurable: yes Dynamic: yes Readable: yes Writable: yes
User Transactions Enabled	Determines whether a connection factory creates sessions that are JTA aware. If enabled, the associated message producers and message consumers look into the running thread for a transaction context. Otherwise, the current JTA transaction will be ignored. However, if the XA Connection Factory Enabled flag is enabled, then this flag must also be enabled to return an XA connection factory. Note: Transacted sessions ignore the current threads transaction context in favor of their own internal transaction, regardless of the setting. This setting only affects non-transacted sessions. MBean: weblogic.management. configuration. JMSConnectionFactoryMBean Attribute: UserTransactionsEnabled	Default: false Dynamic: yes Readable: yes Writable: yes
XA Connection Factory Enabled	Determines whether an XA queue or XA topic connection factory is returned, instead of a standard connection factory. In order for an XA connection factory to be returned, the User Transactions Enabled flag must also be enabled (since it defaults to false). An XA factory is required for JMS applications to use JTA user-transactions, but is not required for transacted sessions. All connections created from an XA factory, whether they are XAConnections or plain Connections, become JTA user-transaction-aware. Note: Transacted sessions ignore the current threads transaction context in favor of their own internal transaction, regardless of the setting. This setting only affects non-transacted sessions. MBean: weblogic.management. configuration. JMSConnectionFactoryMBean Attribute: XAConnectionFactoryEnabled	Default: false Readable: yes Writable: yes
Server Side XA Enabled	Determines whether XA-enabled JMS connections and sessions are always created when this connection factory is invoked from inside a WebLogic Server instance. MBean: weblogic.management. configuration. JMSConnectionFactoryMBean Attribute: XAServerEnabled	Default: false Readable: yes Writable: yes

Attribute Label

Description

Value Constraints

Transaction Timeout

All transactions on connections created with this connection factory will have this timeout value expressed in seconds.

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.

MBean: weblogic.management.
configuration.
JMSConnectionFactoryMBean

Attribute: TransactionTimeout

Minimum: 0

Maximum: 2147483647

Default: 3600

Configurable: yes

Dynamic: yes

Readable: yes

Writable: yes

User Transactions Enabled

Determines whether a connection factory creates sessions that are JTA aware. If enabled, the associated message producers and message consumers look into the running thread for a transaction context. Otherwise, the current JTA transaction will be ignored.

However, if the XA Connection Factory Enabled flag is enabled, then this flag must also be enabled to return an XA connection factory.

Note: Transacted sessions ignore the current threads transaction context in favor of their own internal transaction, regardless of the setting. This setting only affects non-transacted sessions.

MBean: weblogic.management.
configuration.
JMSConnectionFactoryMBean

Attribute: UserTransactionsEnabled

Default: false

Dynamic: yes

Readable: yes

Writable: yes

XA Connection Factory Enabled

Determines whether an XA queue or XA topic connection factory is returned, instead of a standard connection factory.

In order for an XA connection factory to be returned, the User Transactions Enabled flag must also be enabled (since it defaults to false).

An XA factory is required for JMS applications to use JTA user-transactions, but is not required for transacted sessions. All connections created from an XA factory, whether they are XAConnections or plain Connections, become JTA user-transaction-aware.

Note: Transacted sessions ignore the current threads transaction context in favor of their own internal transaction, regardless of the setting. This setting only affects non-transacted sessions.

MBean: weblogic.management.
configuration.
JMSConnectionFactoryMBean

Attribute: XAConnectionFactoryEnabled

Default: false

Readable: yes

Writable: yes

Server Side XA Enabled

Determines whether XA-enabled JMS connections and sessions are always created when this connection factory is invoked from inside a WebLogic Server instance.

MBean: weblogic.management.
configuration.
JMSConnectionFactoryMBean

Attribute: XAServerEnabled

Default: false

Readable: yes

Writable: yes