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 can
happen 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 using the mqsistop command specifying the -q parameter. (The -q parameter is not available on z/OS.) This
issues the WebSphere MQendmqm command
on your behalf in a controlled fashion that shuts down the broker and the
queue manager cleanly.
The execution group terminates abnormally
Scenario: Your execution group processes terminate abnormally.
Explanation: When execution group processes terminate abnormally,
they are restarted automatically by the bipbroker process. If an execution
group process fails, it is restarted three times during each five-minute interval.
The first five-minute interval begins when the execution group is first started.
The broker database table BROKERAAEG contains a column labeled RetryInterval.
This column defines the restart time in minutes. Each row in this table represents
an execution group. The row is populated on the first deployment
of an execution group and RetryInterval defaults to 5.
If you
remove the execution group from the broker configuration, deploy the broker
configuration, and then later add the execution group 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 RetryInterval's value in the database table.