WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Resolving problems that occur after debugging:

This topic contains advice for dealing with some of the common problems that can arise after debugging message flows.

You cannot change a message flow after debugging

  • Scenario: You were debugging, but now your message flow seems to be stuck. When you put a new message in, nothing happens.
  • Explanation: This might be because a message was backed out, but you have not set the Backout requeue name property of your input queue.
  • Solution: Set the Backout requeue name property to a valid queue name (such as the name of the input queue itself) and your flow will become unstuck.

You redeployed a debugged message flow but deployment hangs

  • Scenario: You found problems in your message flow by using the debugger. You changed your message flow and then redeployed it, but now the deployment hangs.
  • Solution: Make sure that when you redeploy the flow to an execution group, the execution group is not still attached to the debugger.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:39


Task topicTask topic | Version 8.0.0.7 | au16613_