See information about the latest product version
How can I diagnose problems?
New users: Use the links in this topic to find out how to debug message flows and get help with troubleshooting problems.
How can I debug and troubleshoot my message flows?
A number of tools and sources of information are available to help you solve problems with your message flows. If you can see errors or warnings in the Problems view in the WebSphere® Message Broker Toolkit, your message flows and related resources might have problems that prevent you from adding them to a broker archive file. Also, your message flows might not work as you expect when they are deployed.
Use the information in the error or warning messages to fix the problem. If you have difficulty deploying message flow resources, see How can I troubleshoot problems when deploying message flows? in this topic for more information. If you have successfully deployed your message flows, you can use the following links to debugging and troubleshooting topics to help you solve any problems.
- How do I use the flow debugger? You can test and debug your message flows by using the debugger in the WebSphere Message Broker Toolkit. By adding breakpoints to your message flows, you can use the debugger to view the path that messages take through your message flow. You can also view the contents of the message passing through the flow, and step through code to view the output messages being constructed. The debugger is launched from the Debug perspective.
- Where can I find useful logs?
Find out where to find useful logs that are used in WebSphere Message Broker.
- How do I use trace? User trace can be used to get further information about problems with messages passing through your message flows. You can use the following sequence of tasks to get user trace to troubleshoot a problem with a message flow:
- How can I resolve problems when developing message flows? Follow this link for information about some common problems when developing message flows.
- How can I resolve problems when developing message models? Follow this link for information about some common problems when developing message models.
How can I troubleshoot problems when deploying message flows?
If your message flows or related resources contain an error, they cannot be added to a broker archive file. Sometimes message flows that are successfully added to a broker archive file can fail to be deployed, for example, because of a problem with the broker or with the message flows. Use the following links to find out how to check the results of deployment and get help solving problems.
- How can I check the results of deployment? Find out how to check the results of a deployment by using the Administration Log view, the mqsideploy command, and the Message Broker API (also known as the CMP API).
- How can I resolve problems when deploying message flows or message sets? Follow this link to find tips on resolving problems when deploying message flows and message sets.
Where can I get other help on troubleshooting and solving problems?
Use the links in this section to find out more information about troubleshooting and how to get support.
- What initial checks can I make? Follow this link to get more in-depth advice on checks to make if you have problems with WebSphere Message Broker.
- How do I deal with problems? Use the links in this topic to find out about common problems that you might see when you use WebSphere Message Broker. Check to see if one of these problems match the symptoms you are observing.
- Where can I get more help with problems? View this topic for links to more techniques for diagnosing problems with WebSphere Message Broker, and links to information about getting support.