![]() |
![]() |
e-docs > WebLogic Server > WebLogic Server Frequently Asked Questions > FAQs: WebLogic Messaging Bridge |
WebLogic Server Frequently Asked Questions
|
FAQs: WebLogic Messaging Bridge
Q. Why did the messaging bridge fail to connect to the source bridge destination?
A. Either an error occurred when configuring the source bridge destination parameters, or the actual source destination is not running and cannot communicate with the messaging bridge.
Note: This troubleshooting scenario for correcting a source bridge destination connection failure also applies to target bridge destinations.
Q. Can the messaging bridge handle two-phase or global transactions between separate WebLogic Server domains or between different releases?
A. Yes, as long as the communication is between source and target WebLogic domains that are both running release 6.1 SP03 or later, and the bridge is configured to use the Exactly-once quality of service.
Also, depending on which service pack of release 7.0 the bridge is running on, you may have to establish a trusted relationship between release 6.1 and 7.0, as follows:
For more information about using the Exactly-once QOS when interoperating between release 6.1 and release 7.0 domains, see "Using the Messaging Bridge To Access Destinations In a Release 6.1 or Later Domain" in the Administration Guide.
Q. I configured the messaging bridge to use the Exactly-once quality of service for two-phase transactions. So why am I getting a "quality of service is unreachable" error?
A. There are some additional configuration requirements for the messaging bridge to handle transactions between WebLogic domains:
UserTransactionsEnabled=true
XAConnectionFactory=true
For more information about using the Exactly-once QOS when interoperating between release 6.1 and release 7.0 or later domains, see "Using the Messaging Bridge To Access Destinations In a Release 6.1 or Later Domain" in the Administration Guide.
Q. Can I configure the messaging bridge to automatically downgrade the quality of service if the Exactly-once service isn't available on either the source or target bridge destination?
A. Yes, just make sure to select the QOS Degradation Allowed check box on the Messaging Bridge
Q. Why do I get a security authorization exception when attempting to forward messages from a WebLogic Server 7.0 GA, SP01, or SP02 destination to a release 6.1 destination?
java.lang.SecurityException: Invalid Subject: principals=[user1]
A. In WebLogic Server 6.1, the trust relationship between two WebLogic Server domains was established if the system password was the same in both domains. For a release 7.0 GA, SP01, and SP02 messaging bridge to communicate with a release 6.1 domain, you must establish a trusted relationship across release the 6.1 and 7.0 domains. A trusted relationship is established when the Credential attribute for one domain matches the Credential attribute for another domain. Therefore, if you want a release 6.1 domain to interoperate with a release 7.0 SP02 or earlier domain, you need to change the Credential attribute in both domains to the password of the "system" user in the release 6.1 domain.
However, for release 7.0 SP03 or later, you do not need to establish a trusted relationship across release 6.1 and 7.0 domains.
Q. I deployed the transactional jms-xa-adp.rar resource adapter on the WebLogic 7.0 domain where the message bridge is running, but I still get a "failed to find bridge adapter" message?
A. You need to associate both the source and target bridge destinations with the appropriate.rar adapters in order for the bridge to communicate with them. For the jms-xa-adp.rar transaction adapter, it must be identified in the Adapter JNDI Name attribute as eis.jms.WLSConnectionFactoryJNDIXA on the JMS Bridge Destination
Note: The "failed to find bridge adapter" message does not necessarily indicate a problem if it only occurs once. However, if it occurs repeatedly, you should check the adapter deployment and the adapter JNDI name used in the source and target bridge destinations.
For more information about the bridge resource adapters, see "About the Bridge's Resource Adapters" in the Administration Guide.
Q. When configuring a source or target messaging bridge destination, do I need to set the Adapter Classpath field?
A. Leave the Adapter Classpath field blank when connecting to source and target destinations that are both running on release 7.0 or later. When connecting to either a source or target destination that is running on release 6.0 or earlier, the Adapter Classpath field must indicate the location of the classes for the earlier WebLogic Server release. When connecting to a third-party JMS provider, the bridge destination must supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
Q. Can the messaging bridge forward durable subscription messages between separate WebLogic Server 6.1 and release 7.0 or later domains?
A. Yes, as long as the domain hosting the bridge is using WebLogic 7.0 Service Pack 1 or later. To enable durable messages across the messaging bridge using the Administration Console, select the Durability Enabled attribute on the Messaging Bridge
Q. How do I enable debugging for the messaging bridge?
A. You can enable debugging for the messaging bridge using either of the followings methods:
-Dweblogic.Debug.DebugMessagingBridgeStartup=true
-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add "DumpToConsole" to the statements show above. For example:
-Dweblogic.Debug.DebugMessagingBridgeStartupDumpToConsole=true
Q. What do the messaging bridge monitoring states indicate on the Monitor Messaging Bridge console page?
A. When monitoring a messaging bridge's state on the Server
Q. Is there another way to monitor the messaging bridge without using the Administration Console?
A. Yes, there is a run-time MBean (MessagingBridgeRuntimeMBean) for each bridge instance. WebLogic Server run-time MBeans provide a snapshot of information about domain resources. When a particular resource in the domain (such as a messaging bridge) is instantiated, an MBean instance is created which collects information about that resource.
The MessagingBridgeRuntimeMBean has a getState() method that currently returns a String ("Active" or "Inactive") and a getDescription() method, which returns a String with more detailed information. The name of a bridge runtime MBean consists of the WebLogic Server instance name and the bridge name. If a bridge named mybridge, runs on WebLogic Server instance named myserver, the bridge runtime MBean will be named myserver.bridge.mybridge.
For more information about using run-time Mbean management commands, see "WebLogic Server Command-Line Interface Reference" in the Administration Guide. For more information about programming MBean monitoring notifications, see "Using WebLogic Server MBean Notifications and Monitors" in Programming WebLogic JMX Services.
Q. Can the messaging bridge use distributed destinations as source and target destinations?
A. Yes, the messaging bridge can send to and receive from distributed destinations. Bea recommends the following configurations:
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |