| Author |
Message
|
| sangminli |
 Posted: Tue Aug 26, 2008 7:20 pm Post subject: mqsideletebroker doesn't work |
 |
|
Voyager
Joined: 26 Aug 2008
Posts: 75
Location: Hangzhou, China
|
hi, i am trying to setup MB environment for exercise. and for some reason i'd like to delete the old ones and create new ones. it was working fine when i was at home with my own computer with this cmds:
mqsideletebroker MQ641BRK
mqsideleteconfigmgr MQ641CM
mqsideleteusernameserver
mqsideletedb MQ641BDB
but when i tried the first cmd on the pc in the office, i just got this:
===============================
C:\Program Files\IBM\MQSI\6.1>mqsideletebroker MQ641BRK
WebSphere MQ queue manager running.
BIP8052E: Unable to delete WebSphere MQ Object 'SYSTEM.BROKER.CONTROL.QUEUE' from Queue Manager 'MQ641B'.
This command attempts to delete a WebSphere MQ Object but was unable to do so. Locate and resolve the problem and retry the command. This could be because a We bSphere MQ channel is still running. If this is the case, stop all WebSphere MQ channels running on behalf of this Queue Manager. If your Message Brokers Tool kit is connected to your configuration manager, you may need to disconnect it as well.
==================================
I stopped all the channels, and toolkit was not connected to the qmgr either. i just found that there are some processes accessing the queue SYSTEM.BROKER.CONTROL.QUEUE, and they don't seem to stop some time later. (the MQ i am using is MQv7 trial edition).
could someone advise how can i delete the broker?
the 2 processes accessing the queue are as follows:
amqfcxba.exe & amqfqpub.exe.
any advice would be greatly appreciated. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Aug 26, 2008 8:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well let's see... It looks like you have either the message broker or the MQbroker still running. Stop both of those and retry the command... You may have to recreate this broker queue... Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sangminli |
| Posted: Tue Aug 26, 2008 8:36 pm Post subject: |
|
|
Voyager
Joined: 26 Aug 2008
Posts: 75
Location: Hangzhou, China
|
| fjb_saper wrote: |
| Well let's see... It looks like you have either the message broker or the MQbroker still running. Stop both of those and retry the command... You may have to recreate this broker queue... Enjoy |
it is on windows, and i've stopped the message broker component. and the queue is still there. the issue is: some programs have the queue open so mqsideletebroker can't do the cleanup. and it terminated with the broker not deleted.. i didn't encounter this issue with MQv6. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 26, 2008 9:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sangminli wrote: |
| fjb_saper wrote: |
| Well let's see... It looks like you have either the message broker or the MQbroker still running. Stop both of those and retry the command... You may have to recreate this broker queue... Enjoy |
it is on windows, and i've stopped the message broker component. and the queue is still there. the issue is: some programs have the queue open so mqsideletebroker can't do the cleanup. and it terminated with the broker not deleted.. i didn't encounter this issue with MQv6. |
Yes and it looks like said component would be the MQ broker (amqfqpub.exe).
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sangminli |
| Posted: Wed Aug 27, 2008 4:56 pm Post subject: |
|
|
Voyager
Joined: 26 Aug 2008
Posts: 75
Location: Hangzhou, China
|
i delete the services forcibly via regedit finally..  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 27, 2008 8:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sangminli wrote: |
| i delete the services forcibly via regedit finally.. |
Bad boy !!! You should have looked in runmqsc or MQExplorer and simply stopped the service!
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sangminli |
| Posted: Wed Aug 27, 2008 8:45 pm Post subject: |
|
|
Voyager
Joined: 26 Aug 2008
Posts: 75
Location: Hangzhou, China
|
| fjb_saper wrote: |
| sangminli wrote: |
| i delete the services forcibly via regedit finally.. |
Bad boy !!! You should have looked in runmqsc or MQExplorer and simply stopped the service!
Enjoy |
i was not able to delete the broker via mqsideletebroker, and i don't like it listed as system service, so i deleted it from the system registry. |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Thu Sep 10, 2009 6:28 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
Hi,
I am facing a similar issue. I am getting error while deleting a Broker :
==========
WebSphere MQ queue manager running.
BIP8052E: Unable to delete WebSphere MQ Object 'SYSTEM.BROKER.CONTROL.QUEUE' from Queue Manager 'XYZ'.
This command attempts to delete a WebSphere MQ Object but was unable to do so. Locate and resolve the problem and retry the command. This could be because a WebSphere MQ channel is still running. If this is the case, stop all WebSphere MQ channels running on behalf of this Queue Manager. If your Message Brokers Toolkit is connected to your configuration manager, you may need to disconnect it as well.
=============
I have removed the broker from the Config mgr Domain from the toolkit. This Broker is stopped but there are 5 process[ 4 instnace of amqfcxba + 1 instnace of runmqbrk ] sticked with queue 'SYSTEM.BROKER.CONTROL.QUEUE' .
I do not want to delete the registry entries..is there any way to delete this broker? Why these two process stuck with queue even Broekr service is stopped?
Cheers,
Aditya |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Sep 10, 2009 6:54 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Restart the Broker QMGR. This will make sure that no <defunct> qmgr handles are lying around. Then try the broker delete once more.
I have seen this with the channel from the Config Mgr still being 'running' and the ipprocs of the queue in question > 0. The restart should solve this.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Thu Sep 10, 2009 7:09 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
| Quote: |
Restart the Broker QMGR. This will make sure that no <defunct> qmgr handles are lying around. Then try the broker delete once more.
I have seen this with the channel from the Config Mgr still being 'running' and the ipprocs of the queue in question > 0. The restart should solve this. |
I have already did this... it does not help. I also kill the process but still it sticks with the queue... seems like a bug?
Cheers,
Aditya |
|
| Back to top |
|
|
| mdmader |
| Posted: Tue Sep 22, 2009 7:57 am Post subject: |
|
|
Newbie
Joined: 17 Apr 2008
Posts: 7
|
Looks like it's been a bit since the last update on this thread.
I didn't see if you had a solution but, since you're using MQ7, did you set the PSMODE=COMPAT in your Queue Manager?
Ran into the same issue yesterday after reinstalling MBTK w/ MQ7. Resolved the problem for me. |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Tue Sep 22, 2009 9:33 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
I am using MQ V6.....
We have also resolved the issue after reinstalling the Broker runtime... |
|
| Back to top |
|
|
| damianharvey |
| Posted: Wed Apr 21, 2010 9:08 pm Post subject: |
|
|
Acolyte
Joined: 05 Aug 2003
Posts: 59
Location: Sydney, Australia
|
Just encountered the same issue.
Solution for me was to open the properties of the Queue Manager and disable Publish/Subscribe.
This freed up the SYSTEM.BROKER.CONTROL.QUEUE and the mqsideletebroker command was able to complete without issue.
Hope this helps.
Cheers,
Damian. |
|
| Back to top |
|
|
| AMuck |
| Posted: Thu Mar 21, 2013 8:10 am Post subject: |
|
|
Newbie
Joined: 09 Dec 2003
Posts: 3
|
| When I get this error, I find the quickest solution is to get and put disable the SYSTEM.BROKER.DEPLOY.REPLY queue and then delete the broker |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 21, 2013 8:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| AMuck wrote: |
| When I get this error, I find the quickest solution is to get and put disable the SYSTEM.BROKER.DEPLOY.REPLY queue and then delete the broker |
It may be the quickest solution, but you're still 3 years too late for even the last poster....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
