Scenario: You run the mqsistop command to stop the
broker, but the system freezes, and does not stop any of the integration
servers.
Explanation: One possible cause is that a message
flow is being debugged and it is currently stopped at a breakpoint. IBM® Integration Bus regards this as a message in
flight situation, and refuses to stop the broker through the normal
command.
Solution: Click Stop debugging in
the Integration Development perspective of the IBM Integration Toolkit. After that operation has completed,
the broker stops.
If you cannot stop the debug session,
end all integration server processes that are associated with that broker
to allow the broker to stop. Your messages are backed out. Click Stop
debugging after the broker restarts.
You cannot stop the broker queue manager
Scenario: You are trying to use the WebSphere® MQendmqm command
to stop a broker queue manager on a distributed system, but it does
not stop.
Explanation: In certain circumstances, attempting
to stop a broker queue manager does not cause the queue manager to
stop. This situation can occur if you have configured any message
flows with multiple threads (you have set the message flow property Additional Instances to a number greater
than zero).
Solution: If you want to stop the broker's queue
manager, stop the broker by running the mqsistop command and specifying
the -q parameter. (The -q parameter
is not available on z/OS®.) This
command runs the WebSphere MQendmqm command
on your behalf in a controlled fashion that shuts down the broker
and the queue manager cleanly.
The integration server ends abnormally
Scenario: Your integration server processes end abnormally.
Explanation: When integration server processes end
abnormally, they are restarted automatically by the bipbroker process.
If an integration server process fails, it is restarted three times during
each five-minute interval. The first five-minute interval begins when
the integration server is first started. RetryInterval
defaults to 5
Remove the integration server from the
broker configuration, deploy the broker configuration, then later
add the integration server, and redeploy the broker configuration. The
row is re-created and RetryInterval is set to its default value of
5.
Solution: To change the default value:
Stop the broker.
Change the value of the RetryInterval in the database
table.
Last updated Friday, 21 July 2017