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 being consumed

This topic describes how to investigate why point-to-point messages are not being consumed from a destination on a service integration bus.

Use this topic if you did not get a response in your application because a message you were expecting did not appear on a queue. The information in this topic applies to local and remote producers, and local and remote consumers.

Perform the following preliminary checks before starting the investigation:
  1. Run the consuming application and check that messages are still not being consumed.
  2. Stop the consuming application.
  3. Determine which messaging engine is hosting the queue point to which messages are being produced. See Determining the location of message points for a destination on a service integration bus.
  4. Click Application servers -> server_name -> Messaging engines -> messaging_engine_name -> [Message points] Queue points -> queue_point_identifier -> [Runtime tab] Messages to view the messages on the queue point. Check that there are messages present that are in the 'Unlocked' state.
    • If there are no messages present, then there are no messages to consume. Run the producing application to produce a test message and check the queue again. If there are still no messages present, the test message has not arrived. Use the topic Investigating why point-to-point messages are not arriving to investigate the problem.
    • If there are messages present but they are not in the 'Unlocked' state, check for other consumers that are consuming from this queue point. If there are other consumers, stop them and repeat the investigation.
  5. Determine which messaging engine the consuming application is connected to. See Determining which messaging engine an application is connected to.
    • If the consuming application is connected to the messaging engine hosting the queue point, check the consuming application for errors, in particular check that the selector in the consuming application matches the available message.
    • [Version 6.0.2]

      If the consuming 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. Display the runtime properties of the messaging engine that the consuming application is connected to, then display the remote message points for that messaging engine and view the list of message requests on the relevant message point.

      If possible, start the consuming application and ensure that it is actively trying to consume a message (the application should be in either a 'receive with wait' state or an 'asynchronous consumer registered' state), then follow the instructions in Investigating why messages are not being consumed via a remote message point or subscription point, while the application is running. If your application cannot remain in an actively consuming state for a significant length of time (long enough to investigate the problem), follow the steps in Investigating why messages are not being consumed via a remote message point or subscription point, while the application is stopped.

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tju_pt2pt_not_consumed.html

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