Interruption in jeromq kills it

It’s known that jeromq don’t like interruptions. But it hate it so much that an interruption at wrong time can kill it:

    @Test(timeout = 1000)
    public void testInterruptedClose() throws Throwable
    {
        ZContext ctx = new ZContext();
        Socket s = ctx.createSocket(SocketType.PULL);
        int port = Utils.findOpenPort();
        s.bind("tcp://*:" + port);
        Thread.currentThread().interrupt();
        try {
            s.close();
        } catch (Exception ex) {
            ex.printStackTrace();
        }
        // Reset the interrupt state
        Thread.interrupted();
        ctx.close();
    }

An exception is of course throws during the close. But as the close is not really finished, the ctx.close will hang, the test fails with a timeout during the zmq.Ctx.terminate().

Is such a catastrophic failure expected ?

[trevorbernard]

I’ve attempted to totally wrap my head around it before but unfortunately, it’s a bit too much effort and low on my personal priority list. The cognitively complexity of the internals of libzmq/jeromq is quite large

[fbacchella]

Fixed in #836