bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Messaging Bridge --> Configuration --> Connection Retry

Tasks Additional Documentation Attributes

Overview

This tab defines connection retry configuration attributes for a messaging bridge. The source and target destinations for a messaging bridge will not always be available. As such, the messaging bridge must be able to reconnect to the destination at some periodic interval. These attributes govern the time between reconnection attempts.

Tasks

Creating a Messaging Bridge

Assigning a Messaging Bridge to One or More Servers, or Clusters, or a Migratable Target

Adding a Note to a Messaging Bridge

Additional Documentation

(Requires an Internet connection.)

"Using a WebLogic Messaging Bridge" in the Administration Guide

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Minimum Delay (seconds) | Defines the minimum amount of time, in seconds, that the messaging bridge will wait before it tries to reconnect to the source or target destination after a failure. This attribute works with the ReconnectDelayMaximum and ReconnectDelayIncrease attributes. After the first failure to connect to a destination, the bridge will wait for the number of seconds defined by ReconnectDelayMinimum. If the second trial also fails, it will increase its waiting time by the number of seconds defined by ReconnectDelayIncrease. The maximum delay time is defined by ReconnectDelayMaximum. Once the waiting time is increased to the maximum value, the bridge will not increase its waiting time anymore. Once the bridge successfully connects to the destination, its waiting time will be reset to the initial value defined by ReconnectDelayMinimum. MBean: weblogic.management. configuration. MessagingBridgeMBean Attribute: ReconnectDelayMinimum | Minimum: 0 Maximum: 9223372036854775807 Default: 15 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Incremental Delay (seconds) | Defines an incremental delay time, in seconds, that the messaging bridge will wait longer between one failed reconnection attempt and the next retry. This attribute works with the ReconnectDelayMinimum and ReconnectDelayMaximum attributes. After the first failure to connect to a destination, the bridge will wait for the number of seconds defined by ReconnectDelayMinimum. Each time a reconnect attempt fails, the bridge will increase its waiting time by the number of seconds defined by ReconnectDelayIncrease. The maximum delay time is defined by ReconnectDelayMaximum. Once the waiting time is increased to the maximum value, the bridge will not increase its waiting time anymore. Once the bridge successfully connects to the destination, its waiting time will be reset to the minimum value defined by ReconnectDelayMinimum. MBean: weblogic.management. configuration. MessagingBridgeMBean Attribute: ReconnectDelayIncrease | Minimum: 0 Maximum: 9223372036854775807 Default: 5 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Maximum Delay (seconds) | Defines the longest time, in seconds, that the messaging bridge will wait between one failed attempt to reconnect to the source or target and the next retry. This attribute works with the ReconnectDelayMinimum and ReconnectDelayIncrease attributes. After the first failure to connect to a destination, the bridge will wait for the number of seconds defined by ReconnectDelayMinimum. Each time a reconnect attempt fails, the bridge will increase its waiting time by the number of seconds defined by ReconnectDelayIncrease. The maximum delay time is defined by ReconnectDelayMaximum. Once the waiting time is increased to the maximum value, the bridge will not increase its waiting time anymore. Once the bridge successfully connects to the destination, its waiting time will be reset to the initial value defined by ReconnectDelayMinimum. MBean: weblogic.management. configuration. MessagingBridgeMBean Attribute: ReconnectDelayMaximum | Minimum: 0 Maximum: 9223372036854775807 Default: 60 Configurable: yes Dynamic: yes Readable: yes Writable: yes