| Author |
Message
|
| raam |
 Posted: Sun May 22, 2011 11:36 pm Post subject: Issue: Unable to stop a Message Flow |
 |
|
Apprentice
Joined: 14 May 2011
Posts: 29
|
Hello.
I am using MB v6.1.0.2 and logged in as user 'mqbrk'. However, I am unable to stop a message flow under an execution group in Prod Env. This is supposedly causing an infinite loop leading to High CPU consumption by the bipconfigmgr process. And below is the error that I am getting:
mqbrk@<hostname>:/opt/IBM/mqsi/6.0/bin >mqsistopmsgflow -i localhost -p 1414 -q <QMgr> -b <Broker> -e <EG1> -m <MsgFlow1>
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1046E: Unable to connect with the Configuration Manager (Either the network is down, the queue manager 'QMgr' is not running, or there is no related listener running on port 1414 (MQ reason code 2059 while trying to connect)).
The utility encountered a problem while attempting to connect to the Configuration Manager's queue manager to put a message to its request queue.
Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the Configuration Manager's queue manager is running and that the current user is able to put messages to its SYSTEM.BROKER.CONFIG.QUEUE. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate.
All components are up and running, and I require assistance to determine what may be missing or what I may not be doing right.
mqbrk@<hostname>:/opt/IBM/mqsi/6.0/bin >id
uid=207(mqbrk) gid=207(mqbrkrs) groups=1(staff),206(mqm)
Thank you. |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon May 23, 2011 12:24 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Are you supplying the config manager's MQ details, not the broker's?
Try stopping the entire broker. |
|
| Back to top |
|
|
| raam |
| Posted: Mon May 23, 2011 12:42 am Post subject: |
|
|
Apprentice
Joined: 14 May 2011
Posts: 29
|
Both the Configuration Manager and the Broker are using the same MQ Queue Manager and they all reside on the same AIX server.
It is I suppose somewhat common for such a setup to exist.
I have already restarted the entire MQ/MB a couple of times, but I sure am unable to stop the message flow. I am afraid that I may be unable to stop other msg flows as well, but I have not tried stopping any others. And there is connectivity to the database and the QMgr and listener are up and running fine.
Thanks for your response. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon May 23, 2011 12:59 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Ultimately you can kill the DataFlowEngine process which does not stop. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon May 23, 2011 2:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The error says that the command received an MQRC 2059. Is the listener on this queue manager, that is supposedly running just fine, listening on port 1414?
Also, I'm sure you're well aware that version 6.0 is out of support now. So hopefully you have plans very soon to migrate to version 6.1 or 7. |
|
| Back to top |
|
|
| raam |
| Posted: Mon May 23, 2011 2:54 am Post subject: |
|
|
Apprentice
Joined: 14 May 2011
Posts: 29
|
Sure, thank you. Killing the process is the only option I have now, I suppose.
And yes, the listener is listening on port 1414.
And we are working towards migrating to V7 for both MQ & MB by August. My process is to first upgrade MB to FP6109, then migrate MQ to v7, and then the toolkit, etc..
and finally migrate MB to v7.
Thanks for your responses  |
|
| Back to top |
|
|
| exerk |
| Posted: Mon May 23, 2011 3:12 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Moving this to the Broker forum...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
