Are there any general recommendation when using ReceptionAwareness, in terms of “keep maximum retry period to X” or “Domibus gets heavily loaded if it needs to keep retrying with Y messages”, or similar?
Example: To keep retrying for 24 hours for about potentially 10000 stuck messages?
Step-by-step guide
Currently Domibus supports only one reception awareness strategy, that is to constantly retry for X max attempts during Y max time.
Example:
In this case Domibus will retry for each received message maximum 4 times during the interval [date -- to -- date+12 minutes]. Please see below a specific example.
Received/Attempt date | 08:03:57 | 08:06:20 | 08:09:20 | 08:12:20 |
Attempt | 1 | 2 | 3 | 4 |
Please note that the received date of the message is taken into account for computing the next attempt date.
If the user expects a lot of messages and knows that C3 might be down for a long time currently there are 2 options:
1) re-submit the message from C1 like you have suggested
2) tweak the receptionAwareness value maybe to a value higher than 24 hours and spread evenly the next attempts, it is difficult to recommend a specific value.
Another solution would be to implement a different strategy in Domibus, a strategy that is more intelligent that takes into account the fact that the receiver is down. This strategy is not currently supported.