You are using the WebSphere Message Broker Toolkit (version 7.0) to debug one of more of your message flows.
You have deployed the message flows to an execution group, set breakpoints, enabled the debug port, and initialized the debugger. However, the debugger does not debug inbound messages, and breakpoints do not seem to function.
The "Brokers" pane in the WebSphere Message Broker Toolkit displays the execution group that you are using. Right-clicking your execution group displays the following message:
"Terminate Debugger (Port is #####)".
In the WebSphere Message Broker Explorer (WebSphere MQ Explorer), right-clicking your execution group shows the following setting is selected:
"Flow Debug Port -> Enable (on port #####)"
In the WebSphere Message Broker Explorer, the "content" pane for your execution group displays the following message:
"Flow Debug Port Disabled (#####)"
Another execution group has been configured to use the same debug port. When the WebSphere Message Broker Toolkit used this port to start the debugger, the original execution group was loaded, and the new execution group was not loaded.
Diagnosing the problem
Using the WebSphere Message Broker Toolkit, you can right-click other execution groups in the "Brokers" pane to determine if any other execution groups use the same debug port.
Using the WebSphere Message Broker Explorer, you can click other execution groups to view their status the in the "content" pane. The execution group that is loaded by the debugger displays the following message:
"Flow Debug Port Enabled (#####)"
Resolving the problem
To resolve this problem, stop the debugger, then edit the JVM Debug port to be unique for each execution group.
WMBT WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI