| Author |
Message
|
| rcrippen |
 Posted: Thu Aug 01, 2002 11:07 am Post subject: mqsistop not stopping |
 |
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
I've looked through some of the previous posts on this subject and after trying some of the suggestions, still have issues.
I'm running WMQI 2.1 csd02 Broker on AIX v4.3.3 and WMQ 5.2 csd04 and DB2 V7.1
I have not been able to stop the broker using the mqsistop command. I have to issue the -i parameter.
I've increased my dbheap to 1200, my app_clt_heap_sz to 1048. What else can I try to get the mqsistop command to successfully finish?
TIA
Rob Crippen |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Aug 01, 2002 9:14 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Rob,
Your DataflowEngine process might be hanging due to some looping in the message flow? After issuing mqsistop command, in another command window please check whether all DataflowEngine processes have shutdown.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Tibor |
| Posted: Thu Aug 01, 2002 10:30 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
|
| Back to top |
|
|
| rcrippen |
| Posted: Fri Aug 02, 2002 4:09 am Post subject: |
|
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
tibor: Thanks, I had seen that post and my broker's timout values are set to 600 for both parameters.
kirani: Thanks also, that makes sense, the only message flow that I have deployed to the execution group is a flow that has a custom plugin node that is looking for a file in a specific directory. However, when I remove this message flow from the execution group and then try to execute the mqsistop command, I get the same results, it won't stop without the -i option.
Any further suggestions would be appreciated.
Rob |
|
| Back to top |
|
|
| Segs |
| Posted: Sat Aug 03, 2002 11:53 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001
Posts: 78
Location: Zurich Financial Services
|
| Have a look at your UDB fixpacks are these up to date? |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Aug 04, 2002 10:19 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Rob,
Plug-in is loaded when the broker is initialized.
Could you un-install the plug-in and see if the mqsistop command works?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| muralihegde |
| Posted: Sun Aug 04, 2002 10:19 pm Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi,
I think it is a known problem of MQSI on AIX. The mqsistop command not able to stop the broker completely.
Usually what happens is that the normal mqsistop command will bring down all the user deployed execution groups but will fail to bring down the default execution group.
If you look at the system log file "syslog.user" for mqsi, you will see these messages.
According to readme file, this is a known problem, you can now safely give "mqsistop -i" command from another terminal window and can see that the broker comes down and the first mqsistop commadn also responds now saying normal broker down. |
|
| Back to top |
|
|
| rcrippen |
| Posted: Mon Aug 05, 2002 8:34 am Post subject: |
|
|
Apprentice
Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY
|
Thanks muralihegde, I looked at the readme and saw the reference you mentioned. Am I reading this right? Is it okay to stop the broker with the -i option as part of normal shutdown in order to get around this "known intermittent problem"?
Kirani: I have removed all the message flows from the default execution group and romoved all JAR files associated with the plugin node.
The following results are seen:
The first time after a system reboot, the mqsistop command completed successfully without the -i option. Subsequent mqsistarts and mqsistops fail to successfully shutdown the broker default execution group without using the -i option.
I feel that the only option here is to use the mqsistop -i option during normal shutdown of the broker until there is a fix to the bug identified in the readme file that muralihegde mentioned.
Thanks to all who responded.
Rob Crippen |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Aug 05, 2002 12:18 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| muralihegde wrote: |
| I think it is a known problem of MQSI on AIX. The mqsistop command not able to stop the broker completely. |
Maybe known but not normal... We have three brokers on two AIX, and I saw this (bad) behavior. But I was vasting time with OS and brokers and since then 'stopping process' is trouble free. |
|
| Back to top |
|
|
|
|
