Hi, could someone explain to me the mechanics of re-processing the failed messages in RSB: - does RSB process other messages while dealing with a failed one, or is the queue blocked until the failing message is removed - how long does RSB try to handle the message? Minutes? Hours? Days? - is there a tool to quickly move failed messages from errors subqueue back to input queue?
My needs are the following (or at least I think they are): - my application is message-based - there will be a number of failing messages because of errors in communication with external systems, network outages or operation timeouts during high load time (I mean application logic failures due to these reasons, not RSB failures, but the application logic is driven by messages) - a failing message shouldn't block the processing of other messages so the rest of the system can work even if one of its peers is not responding - it should be retried after some time - minute, hour, the retrying should continue for 2-3 days until the system gives up (sometimes it takes several hours or a day until an admin spots the problem and fixes it, so the application should catch up with all failing messages afterwards) To avoid the queue congestion with retried messages, the delay between next retries should be increased in exponential way - for example: 5 sec, 10 sec, 30 sec, 1 min, 2 min, 5 min, etc. Thanks Rafal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
