| Author |
Message
|
| rmah |
 Posted: Tue Sep 11, 2007 8:59 am Post subject: "The execution group has not been successfully deployed |
 |
|
Centurion
Joined: 04 May 2007
Posts: 142
|
I get this error when trying to stop all the message flows:
mqsistopmsgflow -i <hostname> -p 1450 -q mqconfig_01 -b mqbroker_01 -w 300
"BIP1028I: Submitting request to the Configuration Manager to stop 'mqbroker_01'...
BIP1047E: The operation could not be completed by the Configuration Manager.
The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: The execution group has not been successfully deployed yet.
Ensure that the Configuration Manager is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses."
I'm using MB 6.0.0.3 on Linux.
Linux 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux.
There are message flows deployed in the exec groups. ps -ef | grep Data returns several message flows, and so does mqsilist <broker name>. They all have pid's assigned to them.
Thought? Thanks in advanced!
Updated: It seems the command line doesn't really tell the truth all the time. The flows have actually stopped, because MQ Explorer shows no Open Input Count on the queues the exec groups listen on. However, the command line shows exec groups running if I issue the mqsilist <broker name> and ps -ef | grep Data command. Does this only happen to me? Or is this a common phenomena??
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Sep 11, 2007 1:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: The execution group has not been successfully deployed yet. |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 11, 2007 2:03 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
mqsilist doesn't provide any information about the "running" status of any objects.
ps -ef doesn't, really, either. It merely shows you if certain processes or threads exist. If you know what you're doing, it *can* tell you some - that a process is frozen or etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Sep 11, 2007 3:38 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| fjb_saper wrote: |
| Quote: |
| The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: The execution group has not been successfully deployed yet. |
|
300 seconds isn't reasonable? I would think 5 minutes is plenty of time...
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 11, 2007 4:24 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| rmah wrote: |
| fjb_saper wrote: |
| Quote: |
| The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: The execution group has not been successfully deployed yet. |
|
300 seconds isn't reasonable? I would think 5 minutes is plenty of time... |
Did you have to wait five minutes before the script returned an error?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Sep 11, 2007 4:27 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| jefflowrey wrote: |
| rmah wrote: |
| fjb_saper wrote: |
| Quote: |
| The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: The execution group has not been successfully deployed yet. |
|
300 seconds isn't reasonable? I would think 5 minutes is plenty of time... |
Did you have to wait five minutes before the script returned an error? |
Nope. It returned the error less than a minute after I issued the command, even with the -w flag.
Actually, I may have misunderstood the use of the -w flag. My understanding is '-w 300' means that the config mgr would wait up to 5 minutes before it would complain it didn't get a response. Is this correct?
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 11, 2007 5:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That is what I believe the -w does, too. But I haven't looked at the documentation recently to be sure.
If that's what it does, then my point is this. You didn't wait the full timeout period. So whatever problem you had, you got a response from the configmgr.
My secondary point is - you don't know anything about what is or is not running from the output of mqsilist. Ergo, you might have gotten the error because you tried to stop a message flow that was already stopped, either on it's own or because the EG it was deployed to was already stopped.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
