We’ve just released ServiceControl 4.17.2.
#2557 Retried messages have empty payloads when full-text indexing is disabled
How to know if you are affected
You are affected if you are using ServiceControl version 4.17.x and you have selected “Disable full-text indexing” when upgrading from the previous version of ServiceControl.
When failed messages are retried using ServicePulse or ServiceInsight, they are sent with an empty payload. ServiceControl logs a warning each time this happens. The destination endpoint drops these messages and does not attempt to process them. The payload data is not lost. After upgrading to 4.17.2 you will be able to retry these failed messages normally.
Should you upgrade immediately
We recommend that all customers upgrade immediately.
Retrying messages that were retried but dropped at destination
To properly retry messages that were previously retried using ServiceControl 4.17.0 or 4.17.1 but not processed, first upgrade ServiceControl to 4.17.2. Then configure ServicePulse to show the Pending Retries tab, and open the ServiceControl log files.
Each message that was retried but not processed due to this bug will appear in Pending Retries and it will have a warning in the log files similar to:
2021-06-01 14:26:08.8635|78|Warn|ServiceControl.Recoverability.ReturnToSender|2fc11223-74a9-4d09-a91b-93866325a820\1113881: Message Body not found in attachment store for attempt Id c22679d4-d2df-485c-a943-ad3a00c6f609
For each of these messages, click the Retry button.
Where to get it
You can download the new version of ServiceControl from our website.
The team in Particular
Please read our support policy for more details.