| Author |
Message
|
| ajakub |
 Posted: Wed Nov 25, 2009 6:02 am Post subject: Problem with TimeoutControl/Timeoutnotification nodes |
 |
|
Newbie
Joined: 25 Nov 2009
Posts: 2
|
Hello,
I am new in Broker so sorry in advance if I ask about something obvious…
The goal of my task is to introduce delay in the flow – every message that reaches input of the flow should be sent to the output with delay e.g. 15s
I have already added TimeoutControl and TimeoutNotification nodes,
Timeout details are configured in following way:
DECLARE delayTime CHARACTER '00:00:15';
DECLARE startTime TIME CURRENT_TIME + CAST(delayTime AS INTERVAL HOUR TO SECOND);
SET OutputLocalEnvironment.TimeoutRequest.Action = 'SET';
SET OutputLocalEnvironment.TimeoutRequest.Identifier = 'T214_TIA_TC';
SET OutputLocalEnvironment.TimeoutRequest.StartDate = CURRENT_DATE;
SET OutputLocalEnvironment.TimeoutRequest.StartTime = startTime;
SET OutputLocalEnvironment.TimeoutRequest.Interval = 0;
SET OutputLocalEnvironment.TimeoutRequest.Count = 1;
SET OutputLocalEnvironment.TimeoutRequest.IgnoreMissed = TRUE;
SET OutputLocalEnvironment.TimeoutRequest.AllowOverwrite = FALSE;
Generally it works fine…. But:
If another message is put into flow before the previous is processed completely (15s delay), it overrides first message and only the second is processed (first one just “disappears”).
Any clues?
Thanks in advance for help!
Regards Andrzej |
|
| Back to top |
|
 |
| napier |
| Posted: Wed Nov 25, 2009 11:13 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2007
Posts: 48
Location: USA
|
| Quote: |
| SET OutputLocalEnvironment.TimeoutRequest.AllowOverwrite = FALSE; |
In this case second message will fail.
Last edited by napier on Wed Nov 25, 2009 11:23 am; edited 3 times in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 25, 2009 11:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| ajakub |
| Posted: Mon Nov 30, 2009 3:27 am Post subject: |
|
|
Newbie
Joined: 25 Nov 2009
Posts: 2
|
Mqjeff, thanks for the link!
The problem was Identifier parameter which was not changed.
Regards Andrzej |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Dec 01, 2009 1:03 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
I personally have always preferred setting msg id/correlId as the identifier in timeout nodes to avoid this problem
_________________
Cheers |
|
| Back to top |
|
|
|
|
