Technical data

18 Using the WebLogic Messaging Bridge
18-14 Administration Guide
QOS Degradation Allowed When selected, the messaging bridge automatically degrades
the requested QOS when the configured one is not available. If
this occurs, a message is delivered to the WebLogic startup
window (or log file). If this option is not selected (false), and
the messaging bridge cannot satisfy the requested QOS, it will
result in an error and the messaging bridge will not start.
Maximum Idle Time
(seconds)
For bridges running in asynchronous mode, this is the
maximum amount of time, in seconds, the messaging bridge
sits idle before checking the health of its connections. For
bridges running in synchronous mode, this dictates the amount
of time the messaging bridge can block on a receive call if no
transaction is involved.
Asynchronous Mode
Enabled
Defines whether a messaging bridge works in asynchronous
mode. Messaging bridges that work in asynchronous mode
(true) are driven by the source destination. The messaging
bridge listens for messages and forwards them as they arrive.
When the value is false, the bridge works in synchronous mode
even if the source supports asynchronous receiving.
Note: For a messaging bridge with a QOS of Exactly-once to
work in asynchronous mode, the source destination
has to support the
MDBTransaction interface
described in the
weblogic.jms.extensions
Javadoc
. Otherwise, the bridge automatically
switches to synchronous mode if it detects that
MDBTransactions are not supported by the source
destination. For more information about
MDBTransactions, see “Using Message-Driven
Beans” in Programming WebLogic Enterprise
JavaBeans.
Table 18-4 Messaging Bridge Attributes on the General Tab
Attribute Description