Investigating why point-to-point messages are not being consumed

There are a set of checks that we can carry out to investigate why point-to-point messages are not being consumed from a destination on a service integration bus. Complete the following preliminary checks before starting the investigation:

Complete the following checks if you did not get a response in the 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.


  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 Servers > Server Types > WebSphere application servers > server_name > [Server messaging] Messaging engines > 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.


Last updated Nov 10, 2010 8:23:07 PM CST