We’ve just released NServiceBus.RavenDB 4.2.3.
How to know if you are affected
You are affected if you use RavenDB persistence and:
- You publish events while using SQS or Azure Storage Queues transports.
- You attempt to select a different database for Saga/Outbox data based on some parameter of the incoming message in a multi-tenant scenario.
ArgumentOutOfRangeExceptionoccurs in the
LegacyAddressclass when the address does not contain a machine name.
- You are unable to set the correct multi-tenant database using the
Should you upgrade immediately
This is not a critical patch and you only need to update if you are affected by the issues outlined above.
The patch has only been released as NServiceBus.RavenDB 4.2.3, using NServiceBus 6.x and RavenDB Client 3.5. It has not yet been backported for any other versions. If you need the functionality backported to an older supported version, please contact support.
Where to get it
You can download the updated version and see the full release notes here:
The team in Particular
Please read our release policy for more details.