Outbox prevents transports from batching outgoing messages

[andreasohlund]

When outbox is enabled, all outgoing messages are forced to use DispatchConsistency.Isolated. This causes transports that support batching, at the time of writing, Azure Service Bus and Amazon SQS, not to use batching but rather send messages one by one. This leads to increased latency and higher costs since the number of message operations increases.

This behavior should not be needed since the outbox will force the transport transaction mode to be ReceiveOnly, which by definition prevents outgoing messages from being enlisted in the receive transaction.

Expected behavior

Dispatch consistency NOT changed on outgoing messages when the outbox is enabled.

Actual behavior

Dispatch consistency changed to DispatchConsistency.Isolated on outgoing messages when the outbox is enabled.

Versions

All supported versions.

Steps to reproduce

Enable the outbox, send more than one message using either Azure ServiceBus or Amazon SQS. Notice that batching is not used.

Relevant log output

Additional Information

Workarounds

Possible solutions

Additional information

[andreasohlund]

We have reviewed this bug and added it to our bug fix queue. However, there is no ETA for when we will get to this bug as it may be prioritized behind other, more urgent, bugs. We will update this issue when it has a team assigned and work begins.

[bbrandt]

@andreasohlund What is the version this regression was introduced or has the issue always existed?

[andreasohlund]

@bbrandt it has always existed