BIP2033

Severity

0 : Information

Message

The broker was forced to stop an execution group process, process ID was <insert_0>.

Explanation

An attempt was made to stop an execution group process. The execution group process would not terminate itself normally and so was forced to terminate.

Response

One reason for this is that the WebSphere Message Brokers executable bipbroker failed unexpectedly. Bipbroker is automatically restarted by executable bipservice. During the restart of bipbroker all execution groups are terminated by bipbroker and then restarted. If executable bipbroker failed during normal shutdown then execution groups may be left running. On broker restart these execution group will be terminated and a new set of execution groups started. A system log message indicating that executable bipbroker failed unexpectedly would indicate this type of problem. Investigate why the executable bipbroker terminated unexpectedly. Ensure that any database in-doubt or un-commited locks held by the execution group are dealt with, this termination should be treated as an abnormal termination of the execution group and handled accordingly. Use the WebSphere documention together with your database documention to determine the best course of action for dealing with 'In-doubt' units of work. Contact your IBM support center if you are unable to determine the cause of the problem.