After closing web socket connection not all OkHttp's threads are terminated

Hi,

I just wrote simple app like this:

final OkHttpClient httpClient = new OkHttpClient();

final WebSocket webSocket = httpClient.newWebSocket(new Request.Builder().url("ws://demos.kaazing.com/echo").build(), new WebSocketListener() {
    @Override
    public void onOpen(WebSocket webSocket, Response response) {
        System.out.println("STARTED!");
    }

    @Override
    public void onClosed(WebSocket webSocket, int code, String reason) {
        System.out.println("CLOSED!");
    }
});

Thread.sleep(1000);

webSocket.close(1000, "Closed.");

Thread.sleep(1000);

Thread.getAllStackTraces().keySet().stream()
        .filter(Thread::isAlive)
        .forEach(System.out::println);

System output:

STARTED!
CLOSED!
Thread[Signal Dispatcher,9,system]
Thread[Okio Watchdog,5,main]
Thread[OkHttp ConnectionPool,5,main]
Thread[main,5,main]
Thread[Finalizer,8,system]
Thread[OkHttp Dispatcher,5,main]
Thread[Reference Handler,10,system]
Thread[Monitor Ctrl-Break,5,main]

It looks like the OkHttp Dispatcher is waiting for something.

After calling:

httpClient.dispatcher().executorService().shutdown();

All OkHttp’s threads are terminated and java process is finally down.

Is it expected behaviour?

I don’t have similar problems when I call http request, the problem occurs only with web sockets.

Best, Adrian

[yay]

I’m calling

client.dispatcher().executorService().shutdown()
client.connectionPool().evictAll()

on all OkHttpClient instances, yet the application does not exit until after the Okio Watchdog thread is done, around 30 seconds after the shutdown has been initiated.

Is there a way to manually shutdown that thread too?

[kevin4dhd]

Alguna solución?