Major Description
If a rollback on two messages happens between three transactional deliveries, and the two messages are redelivered with the same redelivery backoff settings, there is a likelihood that both messages will cause another rollback to happen. If maximumRedeliveries is set too low, or there are a maximumRedeliveries + 1 messages coming in simultaneously, messages may never get delivered. Can we get another option for the clients that adds a random backoff delay adjustment in addition to the constant backoff delay factor? This would end up working like most other collision avoidance algorithms.