Closed undernorthernsky closed 8 years ago
As a quick fix, I removed the support for reading the retries from the partnership. I think your version looks like a plan :)
There is a now a Math.min
version contained. Thanks again for pointing it out
Fixed in release 2.2.5
Works fine, thank you for the quick fix.
I have this setup
Furthermore (in a specific test) the partnership config specifies 3 retries; and I am sending to an URL where there is no(!) server listening (I was trying to verify that retries are working by delaying listener startup). While working on that the test fails like this:
The lowest line is from the actual call to "send"; the chain of bouncing from resender -> message-processor -> sender -> ... gets longer.
This seems to be caused by
AbstractSenderModule::getRetryCount
. The value passed viaaOptions
is ignored if checkingaPartnership
yields a result; I assume aOptions should have priority, otherwise decrementing the counter in the resender module has no effect?This seems to work for me: