Join GitHub today
http client issue with timeouts #50
I noticed an issue with timeouts in the http client. When a timeout is fired by the http client, the underlying netty channel seams to not be closed so the connection is kept alive until the server closes it (if the server closes it). It causes memory and file descriptors leaks. You can easily reproduce it with a log the close callback in netty/create-client and netcat as server.
Here, at Smallrivers, we heavily rely on aleph on production. We would appreciate your help as quickly as possible on this issue.