i noticed that the ruby client installed via gem is different than the one on git. the gem version still has connection leakage when use reserve(timeout).
On Wed, Dec 16, 2009 at 1:03 AM, 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. 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. > > I don't normally have 1MB jobs, but I set the limit high in case it > happens (very hard for us to predict the size of jobs). Jobs over 50k > are probably 1 in a 100,000, so I'm not too worried. > > Thanks! > > > > On Dec 15, 3:48 pm, Keith Rarick <[email protected]> wrote: >> On Tue, Dec 15, 2009 at 6:58 AM, Carl <[email protected]> wrote: >> > Is there a way to create a log file to see what happens, because right >> > now I have no clue what could be causing this. >> >> You can run it without the "-d" flag. When something goes wrong, >> beanstalkd will print out error messages. If the crash is from a >> segfault, you'll have to rely on your operating system to tell you so. >> (And, in that case, a stack trace or a core dump would be very helpful >> to me.) >> >> 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. > > > -- Best regards Linan Wang -- 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.
