How I handle common problems while developing message flows in WebSphere Message Broker
DavidBrickell 270001MT2R Visits (10251)
When developing message flow applications for Websphere Message Broker, I have encountered different types of issues. Fortunately, there are many tools available to help debug and resolve these issues.
Generally I run into issues during one of the following phases of development.
Information about the error can be seen within the description and type. By right clicking the error description, we can choose the Go To option to be taken to the location of the error.
In the case where we see a syntax error reported, we would be taken to the line of code within the ESQL that is causing the issue.
V6.1 common issues
V7 common issues
These are some of the common issues we have seen when developing flows and how to resolve them.
When building a bar file within the toolkit, errors can sometimes occur. Generally these errors appear in a popup window.
Resolving failed deploys in V6.1
Resolving failed deploys in V7
They provide details about which logs to investigate and what steps should be taken when encountering errors upon deploy of message flows or message sets.
If an error occurs while a flow is running, Broker will report the error to the Operating Systems error logs.
When looking at the error code in the Infocenter, three pieces of information is given:
3-Response (How to handle the error)
If a more detailed, step by step look at what is happening within the flow is needed, we can also take a Usertrace. This is useful when determining at what point in the flow an error is occurring.