Posted: Wed Apr 22, 2009 9:11 am Post subject: Background cmd.exe
Master
Joined: 03 Nov 2004 Posts: 211
I stumbled across something and would like to see if anyone else has seen this or knows anything about it.
I'm running WMB V6.0.0.5 on W2K.
We had an issue where we had a script start a bunch of cmd.exe's that didn't have an exit in them. So I had to kill them via taskmgr. Inadvertantly I killed a cmd.exe that was running under the broker id. When I did this I noticed that another cmd.exe under the broker id was started along with copies of bipbroker, biphttplistener and copies of all my dataflowengines. I then killed the cmd.exe a second time and again third instances of bip processes were started along with third instances of all my dataflowengines.
I then issued a mqsistop against the broker and every process that was started was stopped, including copies.
So it appears as though the broker when started kicks off a cmd.exe that is doing something and if you kill that cmd.exe something occurs that results in another broker instance being started.
Just replicated on a 6103 broker...killed the cmd running under the broker id, after a short period of time another bipbroker/httplistener/dfe's get started.
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