On 20/06/2018 13:16, Thomas Stüfe wrote:
Yes, and it typically means that something is seriously broken. We had exactly this early in JDK 11 where some refactoring (to make use of Cleaner) introduced a bug that lead to random closing of sockets. So important that any failures like this are diagnosed quickly.: I am curious whether we now get a bunch of follow up errors, since before we never catched a failing CloseHandle. A typical reason why this could fail would be a double close.
-Alan