On Tue, Dec 15, 2009 at 5:03 PM, Carl <[email protected]> wrote: > I think I found/solve the issue. Somehow my Ruby app was leaking > connections, which was driving the C daemon crazy it seems.
beanstalkd should handle that scenario reasonably. It will start refusing new connections until the number of open connections drops. If you're seeing different behavior, I'd like to fix it. > I've been > able to limit the connection leakage and it seems to be doing much > better now. I also use HEAD of the Ruby client. Would it be possible > to push a release soon? It's much easier to use a gem and it's been a > while. Yeah, I'm (slowly) working on it, with enormous help from several other developers (as you can see in the commit logs). kr -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
