We’ve just released Particular.TimeoutMigration 1.2.1.
- #258 Timeouts due before the tool is run are lost when migrating to RabbitMQ
You are affected if:
- You used the migration tool to migrate timeout messages into the RabbitMQ transport’s delayed delivery infrastructure.
- You migrated timeouts that had already expired or were very close to expiration when the migration was performed.
Messages that should have been migrated are missing and are never delivered.
As long as the cleanup procedure for timeout manager data has not been performed, lost messages can be recovered. Please contact
firstname.lastname@example.org for assistance.
You should upgrade before using the tool to perform more migrations.
You can install the new version from NuGet.
To update an existing global installation, run
dotnet tool update --global Particular.TimeoutMigration.
The team in Particular
Please read our release policy for more details.