Comment 3 for bug 2044097

I haven't seen this on single node/single db since the early 400's builds. Unless @dotj still sees this it could be that its been fixed on the way and happy to close for my case. Suggest we check multi node as David mentions above though.