Archived
This forum has been archived. Please start a new discussion on GitHub.
Thread leak with Java
I've noticed that my server is leaking threads using 3.3.1 and a java client & server.
The specific scenario is that the the client times out the request to the server and every time the client times out the server the thread appears to be leaked. This eventually runs the server out of file descriptors and a hanging death ensues.
Is this a known problem, fixed in a subsequent version, the release notes for 3.4 make no reference to any bugs fixed.
The specific scenario is that the the client times out the request to the server and every time the client times out the server the thread appears to be leaked. This eventually runs the server out of file descriptors and a hanging death ensues.
Is this a known problem, fixed in a subsequent version, the release notes for 3.4 make no reference to any bugs fixed.
0
Comments
-
Possible Idea
Just look for anybody who's seen this or figured things out.
Reading lots of code at the moment, if anybody could shed some light on how the NIO java selector handles the case where the connection is closed -- there's just a few too many functions running around. Wondering if this is communicated to the worker thread or is thread/selector now leaked, thus the write never happens so the cleanup never happens.0