Skip to content

Fix to onNewRegister scenario with multiple REGISTER in a row

Anthony Gauchy requested to merge fix/too_much_register_no_delivery into release/2.2

When receiving two register in a row, ForkMessageContextDbProxy::onNewRegister used to consider the fork as already delivred, even if the reason the second register didn't need a dispatch was that a transaction was already pending.

This situtation could leed in a problem if this transation failed, because this destination will not be delivred again.

Merge request reports