On May 13, 1:23 am, "Keith Rarick" <k...@causes.com> wrote:
So I managed to discover the source of our problem (in case it wasn't
> I suspect a bug in the client library. Can you reproduce this and send
obvious, I am working on the same project as Ilya). It stemmed from
tubes not being "re-watched" after a dropped and re-established
connection. I saw that this problem has been remedied in the latest
code base but we're still using the 0.11.0 version of the ruby
beanstalk-client gem. I guess the newest code has not been released
because for me, "gem install beanstalk-client" always gives me the
0.11.0 version. We had to manually build a gem from the latest git
In any event, the problem seems fixed now though it had nothing to do
In our code, this dropped connection caused a re-connect on the next
Here's the test script:
@beanstalk = Beanstalk::Pool.new('localhost:11300')
# clear the tube of ready jobs
@beanstalk.put('message 1', 65536, 0, 10)
job = @beanstalk.reserve
Running with the 0.11.2 client:
[root@localhost ~]# gem list | grep beanstalk
Here's the output:
[root@localhost ~]# ruby beanstalk-test.rb
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.