WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Investigating why point-to-point messages are not arriving

This topic describes how to investigate why point-to-point messages are not arriving at a destination on a service integration bus.

Why and when to perform this task

Use this topic if you have an application that is producing point-to-point messages in a service integration system, and the messages are not arriving at their destination.

Perform the following preliminary checks before starting the investigation:

Steps for this task

  1. Click Service integration -> Buses -> bus_name -> [Destination resources] Destinations to display the destinations on the relevant bus. Click on the destination and check that the Send allowed check box is selected.
  2. Stop the consuming application. Clear the Receive allowed check box for the destination and save the changes to the master repository. If you do not have dynamic configuration enabled, restart the messaging engine for the changes to take effect. This will prevent any consumers from consuming the test message that you will use to investigate the problem.
  3. Run the producing application to produce a test message with a reliability level greater than best effort (best effort messages can be discarded during normal operation so are not useful for investigating this problem). The following steps describe how to investigate what happens to the test message.
  4. Determine which messaging engine hosts the queue point for the destination to which the messages are being sent, see Determining the location of message points for a destination on a service integration bus.
  5. Click Service integration -> Buses -> bus_name -> [Topology] Messaging engines and check that the messaging engine is running.
  6. From the messaging engine panel click [Message points] Queue points ->queue_point_name [Runtime tab] Messages to view the messages on the queue point. If the message is displayed, it arrived successfully at the messaging engine and the problem has cleared.
  7. Determine which messaging engine the producing application is connected to, see Determining which messaging engine an application is connected to.
  8. [Version 6.0.2] If the producing application is connected to a messaging engine other than the messaging engine hosting the queue point, the messages are being routed through a remote message point. Refer to Investigating why point-to-point messages are not arriving through a remote message point to investigate this scenario.

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tju_pt2pt_not_arriving.html

© Copyright IBM Corporation 2004, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)