MQSeries.net :: View topic

goffinf · Posted: Sun Nov 16, 2008 6:45 am Post subject:

WBIMB version 6.1
Platform: Windows XP

When I try and stop the broker service it always fails (times out trying).

Even if I issue an msqistop <broker> -i it still doesn't stop it.

The only way I can do so is using Microsoft's SysInternals ProcessExplorer to 'kill' the process tree.

Has anyone else experienced this and has an idea of what it might be ?

Failing that. is there any way I can discover why this might be happening using some form of trace (there's nothing in the Windows event log other than it indicating that the 'stop' request *was* issued :-

The IBM WebSphere Message Broker component WBRK61_DEFAULT_BROKER service was successfully sent a stop control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Thanks

Fraser.

Supplementary information:

This message appears in the Windows application log when starting the broker service. I guess its because of using process explorer to kill the process (abnormally) :-

( WBRK61_DEFAULT_BROKER ) The broker was forced to stop an execution group process. The process ID was '2424'.

The execution group process would not stop normally and was forced to terminate.

. This might be because the WebSphere Message Brokers executable bipbroker failed unexpectedly. During the automatic restart of bipbroker by the bipservice executable, all execution groups are stopped and then restarted. If executable bipbroker fails during normal shutdown, execution groups might be left running. When the broker restarts, these execution groups are terminated and a new set of execution groups started. A system log message indicating that executable bipbroker failed unexpectedly indicates this type of problem.

. This should be treated as an abnormal termination of the execution group and handled accordingly.

Investigate why the executable bipbroker stopped unexpectedly.

. Ensure that any database in-doubt or uncommitted locks that are held by the execution group are dealt with.

. Use the WebSphere Message Brokers documentation together with your database documentation to determine the best course of action for dealing with 'in-doubt' units of work.

. Contact your IBM support center if you are