| Author |
Message
|
| samuel_lee2000 |
 Posted: Wed Nov 07, 2007 11:19 pm Post subject: Can we deploy message flow/set while the flow is running? |
 |
|
Novice
Joined: 07 Apr 2002
Posts: 13
|
Hi,
We're looking for some advices on message set/flow deployment practice.
When deploying message set/flow, is it necessary to stop the message flow before deploying the new message set/flow?
Could we simply deploy the message set/flow while the message flow is running because the stop/start message flow command take a long time (given that we have multiple brokers/execution groups)
Also, will the mqsireload ensure the newly deployed message flow/set will be effective? We've heard some previous cases that even though the message flow is deployed successfully, the old message flow is still running in some cases.
Thanks in advance!
Best regards,
Samuel |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 08, 2007 1:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
On what version of broker?
You certainly can on v6.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 08, 2007 3:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can deploy anytime you like.
Messages that are in process will be finished processing, and the flow will be stopped and the new flow deployed and then started.
You do not need to stop the flow first. you do not need to mqsireload unless there's a specific issue.
The only case when an old version of a flow is still running after a succesfull deploy has completed is when there is a phantom executiongroup. And that's an exception situation, and so bad things should be expected to happen.
Phantom EGs don't happen very often.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| samuel_lee2000 |
| Posted: Thu Nov 08, 2007 7:20 am Post subject: |
|
|
Novice
Joined: 07 Apr 2002
Posts: 13
|
Hi Vitor and jefflowrey,
Thanks a lot! We're using WMB v6 on AIX. What I have heard from some colleagues who has some previous real experience is exactly the phantom execution group symptom that you've mentioned.
Is there any known cause/reason for such phantom behaviour so that we can do something to avoid it as we're deploying a mission critical system that can't fail.
Thanks again for your advice and time :>
Best regards,
Samuel |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 08, 2007 8:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Phantom EGs most often result from too many cooks stirring the pot at the same time, or from people taking drastic measures because they're impatient.
Good solid deployment procedures and governance, and staying current with maintenance levels are fundamental to ensuring the production uptime of any system - and will do everything possible to prevent Phantom EGs.
You can also monitor processes to find out if you *have* phantom EGs. Any unexpected number of DataFlowEngines should be investigated.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| samuel_lee2000 |
| Posted: Thu Nov 08, 2007 4:52 pm Post subject: |
|
|
Novice
Joined: 07 Apr 2002
Posts: 13
|
Hi jefflowrey,
Thanks very much for your advice!
It gives us a way to check for the unusual circumstances and in the long term, I definitely agree that a good governance and practice must be in place and that's also my vision to setup in the environment which is new to me.
Thanks again for your time and your advice is really very helpful. Much appreciated !
Best regards,
Samuel |
|
| Back to top |
|
|
|
|
