I must check this but I think it is also using NIO SocketChannel. C.
On Sep 18, 4:12 pm, "Ray Krueger" <[EMAIL PROTECTED]> wrote: > Try switching to the spymemcached client > maybe?http://code.google.com/p/spymemcached/ > > On Thu, Sep 18, 2008 at 7:57 AM, lec <[EMAIL PROTECTED]> wrote: > > > Hi, > > > We are using the memcached JAVA client on Linux (RedHat ES4) with Java > > 1.5.0_16. > > All works almost fine, except for a file descriptor leaks (as > > documented and supposed to be fixed here: > >http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6215050) > > > So, basically, the number of open pipes in the client is constantly > > growing, and the client end's up reaching the defined limit of open > > files. This seems to be a bug in NIO SocketChannel. > > By setting the read timeout to 0 (no time out), pipes are no longer > > created. But having a fully blocking read does not seems to be a very > > good idea. > > > Does anybody experienced such an issue ? Any workaround ? > > > Thanks for your help
