Comment 6 for bug 1773373

I have never been able to trigger the problem. The condition is rare and seems to be related to high network load. It seems that only one particular client (not under my control) triggers this fault by triggering "bad resource ID" errors.

I don't have a core dump. All other threads were still functional and the IOC seemed to work just fine. However, it has been restarted meanwhile.

I cannot easily switch a production system to 3.15. There are too many implications and those are not my systems. But I will apply the change of commit d2b0e920012d4c9bc0eaecc0e092cedd776db578 to 3.14.12.7 to see it it still happens.