| Author |
Message
|
| team |
 Posted: Wed Aug 08, 2007 3:53 am Post subject: Delay |
 |
|
Centurion
Joined: 03 Nov 2006
Posts: 108
|
Hi,
Is there a way to introduce a delay pattern in WBIMB flows.
For example if the DB is down, I want to retry....but only after a defined interval of say 30 seconds or so.
Thanks,
Team |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Wed Aug 08, 2007 3:56 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
|
| Back to top |
|
|
| team |
| Posted: Wed Aug 08, 2007 9:23 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 108
|
Hey thanks elvis....
It works amazing!!
Regards, |
|
| Back to top |
|
|
| team |
| Posted: Thu Aug 09, 2007 1:34 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 108
|
Im using the timer node..however these msgs in flight..how would it deal with a broker shut down.. Won't these messages be lost then?
How does the timer node deal with this, since the messages are pulled off the queue. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Aug 09, 2007 1:52 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
no they wont if you configure the nodes to do so....
in timeOutNotification/control node u can check the option... i cant recall the property name....
_________________
Cheers |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Aug 09, 2007 1:54 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
IgnoreMissed
This controls whether timeouts that occur while either the broker or the timeout notification flow is stopped, are processed the next time that the broker or timeout notification flow is started. The default value is TRUE which means that missed timeouts are ignored by the TimeoutNotification node when the broker or message flow is started. If this value is set to FALSE then the missed timeouts are all immediately processed by the Timeout Notification node when the flow is started.
Note that the Request Persistence property of the TimeoutControl node must be set to Yes or Automatic (with the originating request message being persistent) for the stored timeouts to persist beyond the restart of the broker or the timeout notification flow.
your msgs would contuinue to stay in SYSTEM.BROKER.TIMEOUT.QUEUE
_________________
Cheers |
|
| Back to top |
|
|
|
|
