| Author |
Message
|
| lancelotlinc |
 Posted: Tue Nov 29, 2011 7:24 am Post subject: |
 |
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You can implement any way you want. You asking for advice. No one says you have to follow our thoughts. You are free to implement it the way you see fit.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
 |
| McueMart |
| Posted: Tue Nov 29, 2011 7:50 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
Thanks for your advice - i appreciate your opinion as I have read these forums for a good while and have read a lot of good stuff from you. I really don't get the defensive posturing in your previous post though. Do you want me to confront you and tell you you are wrong and you must do it my way!!!
Now that'd just be silly  |
|
| Back to top |
|
|
| ggriffith |
| Posted: Tue Nov 29, 2011 8:42 am Post subject: |
|
|
Acolyte
Joined: 17 Oct 2007
Posts: 67
|
Not wanting to contradict the 3 well versed gents who seem to be trying to steer this poor newbie away from the timeout nodes. I have been using the timeout nodes for a long time without any issues, and in situations where cron would not be of any use. Also, is cron available on all platforms ? I don't think so. 
_________________
Message Broker since 2.1
MQ since before that |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 29, 2011 9:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ggriffith wrote: |
| I have been using the timeout nodes for a long time without any issues, and in situations where cron would not be of any use. |
Good for you. Lord help that I agree with @lancelotlinc but this is advice.
Take it or ignore it; no-one's going to be offended. Each of us are the only ones who know the full nuances of their site, and are responsible for the solution actually implemented. It's why they pay us the big bucks.
One point though:
| McueMart wrote: |
| It was to discuss how to kick off a message flow when it is deployed - and to ensure that it runs every X seconds with the guarantee that only one instance is ever running concurrently |
You don't need a timer node to kick off a flow when it's deployed - it takes a certain amount of dancing to stop it running immediately! Likewise you don't control the number of concurrent instances with this mechanism.
| ggriffith wrote: |
| Also, is cron available on all platforms ? I don't think so. |
It's not called cron on Windows but there is an equivalent. Likewise it's not on z/OS but there are a number of alternative mechanisms. So which platform doesn't have cron available? Is there a Unix that doesn't provide it? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| McueMart |
| Posted: Tue Nov 29, 2011 10:31 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Quote: |
| You don't need a timer node to kick off a flow when it's deployed - it takes a certain amount of dancing to stop it running immediately! Likewise you don't control the number of concurrent instances with this mechanism. |
Vitor: Can you clarify what you mean by this please? Are you suggesting there is a better , broker based, way to kick off a flow when it is deployed (without using cron etc)? Or are you referring to the actual running state of the flow (i.e. running or stopped)? If its the latter, thats a strange sentiment as most are fully aware that when a flow is deployed its in the 'running' state.
Regarding the concurrent instances: If I have my TimeoutControl set to Automatic , which is the naive way to invoke something every X seconds; then it is possible for multiple of the flow to be running concurrently if one instance the flow takes >X to run. Correct me if im wrong - I dont recall if i tested that! |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 29, 2011 10:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| McueMart wrote: |
| If its the latter, thats a strange sentiment as most are fully aware that when a flow is deployed its in the 'running' state. |
Most are, but the way your comment was written could be read that a timer node was how you kicked off a flow when it was deployed. Bearing in mind that most but not all of our readership know a flow is deployed in a running state, this thread will remain on the forum for time without end and there's a long history of inexperienced people finding & misinterpreting things with Google I thought I should clarify.
| McueMart wrote: |
| Regarding the concurrent instances: If I have my TimeoutControl set to Automatic , which is the naive way to invoke something every X seconds; then it is possible for multiple of the flow to be running concurrently if one instance the flow takes >X to run. Correct me if im wrong - I dont recall if i tested that! |
What I meant was that the number of instances of the flow has nothing to do with how it's started, timed or otherwise.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| McueMart |
| Posted: Tue Nov 29, 2011 10:51 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Quote: |
| What I meant was that the number of instances of the flow has nothing to do with how it's started, timed or otherwise. |
I'll have a play with this tomorrow but from what I recall through experimentation, the TimeoutNotification doesnt have an Additional Instances setting so if its set to Automatic , you will only run with one instance of the flow; whereas if its set to controlled - you can in theory set it up so that a number of instances of the flow run concurrently (e.g. you send a bunch of control messages for the TimeoutNotification to happen at X time). |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 29, 2011 11:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| McueMart wrote: |
| the TimeoutNotification doesnt have an Additional Instances setting so if its set to Automatic , you will only run with one instance of the flow; whereas if its set to controlled - you can in theory set it up so that a number of instances of the flow run concurrently (e.g. you send a bunch of control messages for the TimeoutNotification to happen at X time). |
That's not entirely how I understand it. If OperationMode is Automatic you'll get 1 and only 1 message per interval but if the previous triggered instance of the flow is still running and the AdditonalInstances > 0 then you'd get another running flow I believe. If OperationMode is Controlled then you can get a paired message for each instance of the flow that's running but again that's controlled by the number of additional instances defined to the flow in question and not how it's started.
I'll be interested in the results of your experiments.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
