Default Messaging Provider Problem Determination - IBM Redbooks

Symptom: Messages disappear when using an MQ link
In this problem scenario, you have defined a connection to WebSphere MQ as a
foreign bus. You have two application servers and two messaging engines and a
foreign bus and MQLink to connect to WebSphere MQ. You are expecting
messages to flow to and from the MQ queue manager but this is not happening.
See Figure 10 as an example of the topology.
WebSphere Application Server V6 Cell
AppServer1
ME1
Deployment Manager Node
Deployment
Manager
Queue Point
Node 1
Node Agent
Service Integration Bus
Members = {AppServer 1, AppServer 2}
Destination localized to
queue point on ME1
Figure 10 Topology of bus connection to WebSphere MQ
AppServer2
ME2
MQLink
Foreign bus to
Websphere MQ
Websphere
MQ
Note: Be careful when defining the WebSphere MQ link definitions. The
Queue manager name field can be confusing. This defines a virtual name
given to the current bus so that the remote queue manager can address
messages to it.
In this scenario, the basic cause of the problem is that ME1 was restarted. The
message producer sends messages using WebSphere MQ to the application on
Appserver1. The message producer, WebSphere MQ, and the bus appear to be
working fine. However, the messages are not arriving at ME1. Using the
WebSphere Application Server V6: Default Messaging Provider Problem Determination 27