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.

• Verify whether the bridge's source destination is correctly configured, by making sure that the following fields on the JMS Bridge Destination Configuration page have been properly completed:

  • Connection URL—this must be the URL of the JNDI provider used to look up the connection factory and actual destination.

  • Destination JNDI Name—this must be the JNDI name of the actual destination mapped to the source bridge destination.

  • Connection Factory JNDI Name—this must be the connection factory used to create a connection for the actual destination mapped to the source bridge destination.

  • User Name/Password—ensure that this user ID has permission to access the actual source destination.

• Verify that the actual source queue or topic destination mapped to the source bridge destination is running and healthy, as follows:

  • Is the WebLogic Server instance hosting the source destination running?

  • Is the JMS server hosting the source destination correctly deployed?

    Note:

    This troubleshooting scenario for correcting a source bridge destination connection failure also applies to target bridge destinations.

Normally, a messaging bridge should forward all messages. If some messages are not being forwarded, here are some possible reasons:

• Some messages may have an expiration time, in which case either the JMS provider for the source or target destination expires the message.

• If you configured the bridge source destination to specify a selector filter, only the filtered messages are forwarded.

• A bridge does not directly provide an option to automatically move messages to an error destination, or to automatically delete messages, after a limited number of forward attempts. However, a JMS provider may provide such an option, which could, in turn, effect any messages on the bridge source destination. If a redelivery limit option is enabled on the JMS provider that hosts the bridge source destination, consider reconfiguring the provider to prevent the bridge automatic retry mechanism from causing messages to exceed the redelivery limit.

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 Æ Configuration tab for both the source and target bridge destinations.

For more information about the bridge resource adapters, see Resource Adapters.

Leave the Adapter Classpath field blank when connecting to source and target destinations that are both running in WebLogic Server instances. When connecting to a third-party JMS provider, the bridge destination must supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.

You can enable debugging for the messaging bridge using either of the followings methods:

• Add the following lines to your WebLogic start script (before the weblogic.Server line):

  -Dweblogic.debug.DebugMessagingBridgeStartup=true
  -Dweblogic.debug.DebugMessagingBridgeRuntime=true

• Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:

  DebugMessagingBridgeStartup="true"
  DebugMessagingBridgeRuntime="true"
  

After debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default.

Yes, the messaging bridge can send to and receive from distributed destinations. Oracle recommends the following configurations:

• If the source is distributed destination, the bridge is pinned to one of the members when it connects to the destination. It stays connected only to that member until it reconnects. The bridge does not receive messages from the other members of the distributed destination. Therefore, the best practice is to configure one bridge for each member of a distributed destinations using the member's JNDIName.

• If the target is a distributed destination, the best practice is to send to the distributed destination using the distributed destination's JNDIName and disable server affinity. This allows the distributed destination to load balance incoming messages.

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 is named myserver.bridge.mybridge.

For more information, see:

• Introduction and Roadmap in Developing Custom Management Utilities Using JMX for Oracle WebLogic Server.

• Using the WebLogic Scripting Tool in Understanding the WebLogic Scripting Tool.

Yes, a bridge can be targeted to any type of cluster. See the next FAQ entry for more information about tuning a bridge that is cluster-targeted.