Messaging Bridge --> Configuration --> Transactions

Messaging Bridge --> Configuration --> Transactions

Tasks Related Topics Attributes

Overview

This tab defines the transaction attributes for a messaging bridge, including setting transaction timeout intervals, transaction batch sizes, and batch intervals.

Tasks

Configuring a Messaging Bridge Instance
Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target

Related Topics

Simple Access to Remote or Foreign JMS Providers

Attributes

Attribute Label

Description

Value Constraints
Transaction Timeout The amount of time, in seconds, that the transaction manager will wait for each transaction before timing it out. Transaction timeouts are used when the QOS for a bridge requires transactions. If a bridge is configured with the Exactly-once QOS, the receiving and sending is completed in one transaction. MBean: weblogic.management.
configuration.
MessagingBridgeMBeanAttribute: TransactionTimeout Minimum: 0Maximum: 2147483647Default: 30Dynamic: yes
Batch Size The number of messages that are processed within one transaction. Note: This attribute only applies to bridges that work in synchronous mode and whose QOS require two-phase transactions. MBean: weblogic.management.
configuration.
MessagingBridgeMBeanAttribute: BatchSize Minimum: 0Default: 10Dynamic: yes
Batch Interval (milliseconds) The maximum time, in milliseconds, that the bridge will wait before sending a batch of messages in one transaction, regardless of whether the Batch Size amount has been reached or not. This attribute only applies to bridges that work in synchronous mode and whose QOS require two-phase transactions.The default value of -1 indicates that the messaging bridge should wait until the number of messages reaches the Batch Size amount before it completes a transaction. However, internally the message batch will be timed out before the transaction times out, and the transaction will be committed regardless of whether the Batch Size amount has been reached or not.Caution: This value should not be set higher than the Transaction Timeout value. Otherwise, if there is not enough volume to make a batch of messages within the time specified by the Batch Interval value, all pending batched messages may be rolled back and resent. In some cases, this may result in an infinite loop.MBean: weblogic.management.
configuration.
MessagingBridgeMBeanAttribute: BatchInterval Default: -1Dynamic: yes

Attribute Label	Description	Value Constraints
Transaction Timeout	The amount of time, in seconds, that the transaction manager will wait for each transaction before timing it out. Transaction timeouts are used when the QOS for a bridge requires transactions. If a bridge is configured with the Exactly-once QOS, the receiving and sending is completed in one transaction. MBean: weblogic.management. configuration. MessagingBridgeMBeanAttribute: TransactionTimeout	Minimum: 0Maximum: 2147483647Default: 30Dynamic: yes
Batch Size	The number of messages that are processed within one transaction. Note: This attribute only applies to bridges that work in synchronous mode and whose QOS require two-phase transactions. MBean: weblogic.management. configuration. MessagingBridgeMBeanAttribute: BatchSize	Minimum: 0Default: 10Dynamic: yes
Batch Interval (milliseconds)	The maximum time, in milliseconds, that the bridge will wait before sending a batch of messages in one transaction, regardless of whether the Batch Size amount has been reached or not. This attribute only applies to bridges that work in synchronous mode and whose QOS require two-phase transactions.The default value of -1 indicates that the messaging bridge should wait until the number of messages reaches the Batch Size amount before it completes a transaction. However, internally the message batch will be timed out before the transaction times out, and the transaction will be committed regardless of whether the Batch Size amount has been reached or not.Caution: This value should not be set higher than the Transaction Timeout value. Otherwise, if there is not enough volume to make a batch of messages within the time specified by the Batch Interval value, all pending batched messages may be rolled back and resent. In some cases, this may result in an infinite loop.MBean: weblogic.management. configuration. MessagingBridgeMBeanAttribute: BatchInterval	Default: -1Dynamic: yes