Hi everyone,
We’ve just released ServiceControl 6.6.2.
Fixed bugs
- #4976 Failed messages retried with Edit & Retry get stuck in the connector poison queue
How to know if you are affected
You are affected if you are:
- using the Particular Platform with MassTransit based endpoints using the MassTransit connector for ServiceControl
- using the “Edit & Retry” functionality to resubmit a message
Symptoms
A failed message that is edited before being retried (via Edit & Retry functionality) does not get back to the input queue of the MassTransit consumer.
The connector logs show an error similar to:
Service[0] Moved message to Particular.ServiceControl.Connector.MassTransit_return.poison. ConversionException: Conversion from ServiceControl failed.
---> System.InvalidOperationException: Messages is expected to have 'ServiceControl.Retry.AcknowledgementQueue' header.
When to upgrade
You should upgrade immediately if you are affected. Otherwise, you should upgrade during your next maintenance window.
Where to get it
You can download the new version of ServiceControl from our website or Docker Hub.
Please read our support policy for more details.
With thanks,
The team in Particular