| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP8019E when trying to do "mqsistop" |
« View previous topic :: View next topic » |
| Author |
Message
|
| Guava72 |
 Posted: Tue Nov 02, 2004 7:20 pm Post subject: BIP8019E when trying to do "mqsistop" |
 |
|
Apprentice
Joined: 06 Jun 2003
Posts: 46
Location: Champaign, IL
|
Hi,
I only saw 1 other post on this error and it didn't really apply. I'm using MQSI 2.1 CSD06 on HP-UX 11. Along with it, we're using WMQ 5.3 CSD05 and DB2 7.1.0.55.
We recently installed a Broker on this HP machine, and whenever we try to issue "mqsistop <brokername>", it gives BIP8019E and says there is already a command to stop the broker OR it is not running. When I do "mqsilist <brokername>, I see procs for the DataFlows (execution groups), and those procs show up with "ps -ef".
I know this is causing unnecessary connections to the DB and might also be why our app is not working. Can anyone offer any insight on how to fix this? Thanks!! |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Nov 02, 2004 11:39 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Can you explain the problem your app is facing? As far as the DB connection goes, you can force/kill them after you stop the Broker.
_________________
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 |
|
|
| Guava72 |
| Posted: Wed Nov 03, 2004 7:18 am Post subject: BIP8019E when trying to do "mqsistop" |
|
|
Apprentice
Joined: 06 Jun 2003
Posts: 46
Location: Champaign, IL
|
Hi Kirani,
I'm not a developer (I'm Infrastructure), so I don't know exactly what is wrong, but basically when feeding an XML to our Broker's "input" queue, it is going to the general "failure" queue we have set up.
It may or may not be related to the problem of mqsistop not working, but ever since we created this broker on HP a few days ago, it's not once shut down properly. And having to kill the bip/Data procs and go into DB2 and force all apps off is (of course) not really a good option! :)
So since the Broker is not behaving properly, I'm assuming this is causing our XML's not to flow. Thanks for any help.
--Ryan |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Wed Nov 03, 2004 8:00 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
When you use mqsistop <brkrName> it will not end the broker immediatly...you have to use mqsistop with -i option. If the command is already running you cant issue the same command...if the msgs are going to error queue..means there is some problem with the flow...do you have any trace????make sure that non of the Dataflow Engines are taking long time...
Thanks,
Chandra. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
