This patch release has the following bug fixes.
- #2700 Distributor stops handing out work to Workers after restart
- #2584 Corrupted MSMQ Message Headers may result in message loss
Bugs
#2700 Distributor stops handing out work to Workers after restart
We've discovered an issue where a distributor will stop handing out message to workers if you first restart a worker and then its distributor. If there is no traffic from the distributor to the worker between the restarts, the distributor might stop sending messages to the worker completely. Should that happen the following info message will be logged over and over by the distributor Session ids for Worker at X do not match, so popping next available worker. The distributor will also be unable to distribute more work to the workers.
How to know if you're affected:
- the distributor repeatedly logs
Session ids for Worker at X do not match, so popping next available worker. - the distributor's main input queue has a lot of messages that are not being distributed to workers.
Workaround:
- Restarting the distributor will fix the issue temporarily, but it can re-emerge later if the distributor and a workers is restarted in succession.
What to do if you're affected:
- Please update your distributor to the latest version. When upgrading the distributor between major versions, it is important that you upgrade as prescribed, so that the workers are properly registered with the distributor.
- This fix does not affect the workers hence, no need to update the workers.
#2584 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent, for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget