Author |
Message
|
novice |
Posted: Fri Sep 16, 2005 7:18 am Post subject: WBIMB Timer, Timeout |
|
|
Apprentice
Joined: 20 Jun 2005 Posts: 37
|
Hi!
I need a reliable timeout mechanism within the message broker. I thought about using the nodes aggregate request and reply to implement the timeout functionality.
The timer will have to run till to 3 hours.
Is this a good idea to use these nodes, are they usable for this purpose?
Are there any inconveniences with these nodes?
Has somebody done already something similar?
What could be a nicer solution?
Best regards |
|
Back to top |
|
 |
wschutz |
Posted: Fri Sep 16, 2005 8:08 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Brover V6 has two new timout nodes, but I'm not sure whether they would help you. Can you explain in more detail what you are trying to accomplish? _________________ -wayne |
|
Back to top |
|
 |
novice |
Posted: Mon Sep 19, 2005 2:29 am Post subject: |
|
|
Apprentice
Joined: 20 Jun 2005 Posts: 37
|
We are using broker version 5.
I need a timeout mechanisim for the following issue:
The broker receives messages one after another. they are stored into a db. when all messages (is a fixed value) have been received the broker goes on with the processing of these messages (the messages are read from the db). please don't question this point - it has to be like that.
when not all messages are received - whatever the reason is - the processing has to go on anyway. that's the case i need a timeout mechansim. after 2 hours the processing of the messages that are stored into the db has to continue in spite of that not all have been received. |
|
Back to top |
|
 |
wschutz |
Posted: Mon Sep 19, 2005 3:04 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
with v5, I think your options are limited to;
1. writing a custom plugin node to do this -or-
2. using some external event to drive a flow after two hours.
with v6 (available Sept 30th), this is exactly what timeout nodes are provided for. You can set a timer to go off in two hours, if you get all your messages, you can cancel the timer, if not, it would go off and drive a message flow of your choosing. _________________ -wayne |
|
Back to top |
|
 |
elvis_gn |
Posted: Mon Sep 19, 2005 3:17 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
I think in the current situation (with v5.0) you should use the Aggregation nodes and try, set the timer to two hours starting the moment the first message is received.... |
|
Back to top |
|
 |
JT |
Posted: Mon Sep 19, 2005 6:31 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
Does the last message distinguish itself from the others?
Is there a count available of the total number of messages ? |
|
Back to top |
|
 |
|