| Author |
Message
|
| Nizam |
 Posted: Thu Jul 15, 2004 4:55 pm Post subject: MQSISTOP Broker Problem |
 |
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
Hi guys,
I have a problem stopping the broker on WBIMB 5.0 on Windows 2000 server.
I tried to stop and start my message flows from the toolkit, I got a message saying that my start and stop were successful, but the tool kit was not refreshing.
I thoght I need to recycle my broker.
I issued the command MQSISTOP broker but it never ended, I terminated the command by issuing a ^C.
But later when I issue the MQSISTOP I get an error message 'BIP8016E'.
Has anyone got this problem and how did you solve it.
I could not find any information on the error code.
Thanks |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Jul 15, 2004 10:27 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Did you try using mqsistop -i command? Look for any hanging/looping Dataflowengine process in the memory and try to kill it. Also try to kill any bipbroker service.
_________________
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 |
|
|
| JT |
| Posted: Fri Jul 16, 2004 6:45 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Nizam wrote: |
I tried to stop and start my message flows from the toolkit, I got a message saying that my start and stop were successful, but the tool kit was not refreshing.
I thoght I need to recycle my broker.
|
Instead of recycling the broker, try doing a mqsireload of the execution group.
| Nizam wrote: |
| I could not find any information on the error code. |
| Quote: |
BIP8016
_______________________
Severity
20 : Error
_______________________
Message
Unable to stop component.
_______________________
Explanation
A request to stop this component was refused.
_______________________
Response
Investigate the reason for this failure and reissue the command. The problem may be that the component was in the process of being stopped or started, in this case just reissue the command. It may be that the command could not be issued because of insufficient userid permissions. If you are unable to resolve the problem, contact your IBM support center. |
|
|
| Back to top |
|
|
| Nizam |
| Posted: Sat Jul 17, 2004 2:20 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
Hi kiran & JT,
I have tried mqsistop with -i option. It worked fine. But later I tried to stop and start the same broker several times, and I am experiencing the same problem again.
when i try to deploy to the broker it says that are still outstanding jobs to be deployed.
Is it related to tuning the database. I am using DB2 8.1.
I haven't tried the mqsireload yet....
Thanks |
|
| Back to top |
|
|
| kirani |
| Posted: Sat Jul 17, 2004 10:22 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Well, it seems you are having with some message flow that's causing this problem. As far as the outstnading deploy is concerned you can get rid of that by doing a "force deploy" of an EG or the Broker. If that doesn't solve the problem then you can go into Configmgr database and delete the entry for your broker where the state is DEPLING.
| Code: |
delete from CBROKER where csection = 'DEPLING'
|
_________________
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 |
|
|
| Nizam |
| Posted: Mon Jul 19, 2004 6:25 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
Hi Guys,
I tried the mqsireload but I have the same problem again.
I even tried the delete from CBROKER where CSECTION='DEPLING' , it says there was no row found.
I still cannot deploy any stuff to the broker. |
|
| Back to top |
|
|
| JT |
| Posted: Mon Jul 19, 2004 6:33 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| when i try to deploy to the broker it says that are still outstanding jobs to be deployed |
Cancelling the last deployment should take care of this (within the toolkit, right-click on the Broker Domain and select Cancel Deployment).
Is there a message build-up in SYSTEM.BROKER.EXECUTIONGROUP.QUEUE on the broker queue manager? |
|
| Back to top |
|
|
| Jack W. Khaw |
| Posted: Mon Jul 19, 2004 11:57 am Post subject: stopping the broker |
|
|
Newbie
Joined: 08 Jul 2004
Posts: 7
|
I think you have redeployed too many times and the Broker is in no-no land.
Stop the Broker service. Clean out all the System.BROKER.... queues and make sure they are all 0 in current depth. Re-start the broker service.
If this does not fix it, delete and recreate broker from the command window.
_________________
jkhaw |
|
| Back to top |
|
|
| MQGuy2000 |
| Posted: Mon Jul 19, 2004 12:51 pm Post subject: |
|
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
reg:
delete from CBROKER where csection = 'DEPLING'
Is it not
delete from CBROKER where csection = 'DPLING' |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Jul 19, 2004 1:15 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Yes, it's DPLING. Thanks for pointing that out.
_________________
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 |
|
|
| Nizam |
| Posted: Tue Jul 20, 2004 5:26 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
Thanks for your replies guys.
I restarted the server and used Cancel Deployment from the Work bench.
There were messages piled up on SYSTEM.BROKER.EXECUTIONGROUP.QUEUE. Some of the messges were stop execution group and the execution group was already deleted.
I recreated the execution group with the same name and then used cancel deployment.
I am not sure which one worked.
Thanks anyways, the discussion was really useful, |
|
| Back to top |
|
|
|
|
