Scenario: You run the mqsistop command to stop the
integration node, 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 integration node through the normal
command.
Solution: Click Stop debugging in
the Integration Development
perspective of the IBM Integration Toolkit. After that operation has completed,
the integration node stops.
If you cannot stop the debug session,
end all integration server processes that are associated with that integration node
to allow the integration node to stop. Your messages are backed out. Click Stop
debugging after the integration node restarts.
You cannot stop the integration node queue manager
Procedure
Scenario: You are trying to use the WebSphere® MQendmqm command
to stop an integration node queue manager on a distributed system, but it does
not stop.
Explanation: In certain circumstances, attempting
to stop an integration node 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 integration node's queue manager, stop the integration node first by running the mqsistop command, and then stop the queue
manager.
The integration server ends abnormally
About this task
Procedure
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
integration node configuration, deploy the integration node configuration, then later
add the integration server, and redeploy the integration node configuration. The
row is re-created and RetryInterval is set to its default value of
5.
Solution: To change the default value:
Stop the integration node.
Change the value of the RetryInterval in the database
table.