| Author |
Message
|
| Omuch |
 Posted: Sun Mar 25, 2012 1:09 am Post subject: TimeoutControl node |
 |
|
Acolyte
Joined: 23 Mar 2012
Posts: 54
|
Hi
I have a flow with TimoutNotification node + TimeoutControl node.
I send message with the right parametrs to the TimeoutControl and i see in debug that the message get out from the out terminal of the TimeoutControl, but nothing changed in the TimeoutNotification.
Any idea?
Thanks. |
|
| Back to top |
|
 |
| kash3338 |
| Posted: Sun Mar 25, 2012 2:43 am Post subject: Re: TimeoutControl node |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Omuch wrote: |
Hi
I have a flow with TimoutNotification node + TimeoutControl node.
I send message with the right parametrs to the TimeoutControl and i see in debug that the message get out from the out terminal of the TimeoutControl, but nothing changed in the TimeoutNotification. |
Can you give more details on your flow design?
How many TimeoutNotiofication do you have and whats the flow design sequence?
What message do you send to TimeoutControl node? |
|
| Back to top |
|
|
| Omuch |
| Posted: Sun Mar 25, 2012 9:25 am Post subject: |
|
|
Acolyte
Joined: 23 Mar 2012
Posts: 54
|
I have one TimeoutNotiofication that triggers a SOAP request and in parallel
one TimeoutControl, It looks like this:
TimeoutNotiofication -> Compute node -> SOAPRequest
MQinput -> Compute Node -> TimeoutControl node
The message is:
<TimeoutRequest>
<Action>SET </Action>
<Identifier>the Identifier </Identifier>
<StartDate>TODAY</StartDate>
<StartTime>NOW</StartTime>
<Interval>10</Interval>
<Count>-1</Count>
<IgnoreMissed>TRUE</IgnoreMissed>
<AllowOverwrite>TRUE</AllowOverwrite>
</TimeoutRequest> |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Mar 25, 2012 9:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
This is kind of a crazy design.
Why not just MQInput->SOAPRequest?
Why the need to schedule when a request is made this way? Use a real scheduler that can run amqsput or something. |
|
| Back to top |
|
|
| Omuch |
| Posted: Sun Mar 25, 2012 10:50 am Post subject: |
|
|
Acolyte
Joined: 23 Mar 2012
Posts: 54
|
I have an internal service, that I need to schedule every 24 hours.
what you mean by "request is made this way"? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Mar 25, 2012 11:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Mar 25, 2012 1:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| You could use a cron job and use amqsput to send a message to a flow that was MQInput->SOAPRequest, instead of trying to do this. |
Because:
If this is not supposed to run every 24 hours but at a specific time every day, a number of things can reset the node so that it either fires 24 hours after reset or doesn't fire at all. The cron utility is immune to this.
You should seriously rethink all aspects of this design from scheduleing to file handling.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Mar 26, 2012 5:35 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
It seems you may be attempting to track state in WMB. Classic ESB implementations use WMB as a stateless object. Find some other way to track state besides WMB.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 26, 2012 6:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| It seems you may be attempting to track state in WMB. Classic ESB implementations use WMB as a stateless object. Find some other way to track state besides WMB. |
There's no reason to assume that all uses of WMB must be an ESB.
There's no reason to assume that all uses of WMB *are* an ESB.
There's no reason to assume that an attempt to use WMB as a scheduler has anything to do with an attempt to treat WMB as a stateful engine.
There are several important solutions built on top of WMB that incorporate stateful datastores. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Mar 26, 2012 10:11 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mqjeff wrote: |
| lancelotlinc wrote: |
| It seems you may be attempting to track state in WMB. Classic ESB implementations use WMB as a stateless object. Find some other way to track state besides WMB. |
There's no reason to assume that all uses of WMB must be an ESB.
There's no reason to assume that all uses of WMB *are* an ESB.
There's no reason to assume that an attempt to use WMB as a scheduler has anything to do with an attempt to treat WMB as a stateful engine.
There are several important solutions built on top of WMB that incorporate stateful datastores. |
My comments were clear regarding the "Classic" use of an ESB. In addition, IBM documentation specifies the same:
| Quote: |
| Use message flows only for performing mediation activities like transformation, translation, protocol conversion, message enrichment, and routing. Message flows should be stateless engines in the mediation activities. |
http://www.ibm.com/developerworks/websphere/library/techarticles/0809_kudikala/0809_kudikala.html
Of course, anyone can break the rules. If someone wanted a hybrid, they could make a stateful message flow. IMHO (thanks Vitor), there are better places to track state than inside a message flow.
| Quote: |
| Given the stateless transactional nature of an ESB, high performance is a given. It's not uncommon for an ESB to handle millions of messages each day in a large organization. |
http://www.ibm.com/developerworks/websphere/library/techarticles/0803_fasbinder2/0803_fasbinder2.html
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
