Lesley Walker wrote:
Howard Chu wrote:
This is most likely ITS#4813, fixed in 2.3.34. As noted in that ITS, it's a bit tricky to manually reproduce the problem since it's quite timing dependent.
Many thanks for the confirmation. Is the fix in the provider or the consumer? Or both?
The fix is in the provider.