On Thu, Nov 5, 2009 at 12:44 PM, mwlang <[email protected]> wrote:
> How can I get at those reported errors and do something about them?
In short, yes, they are getting swallowed. In the beanstalk client
gem, search for "rescue Exception" in
lib/beanstalk-client/connection.rb. There is a reason for catching
exceptions like that -- if you have several beanstalkds running, and
one is down, you (might) still want to connect and use the rest so
that service isn't interrupted. But this is a ham-fisted way to
accomplish that goal, and it causes other problems, such as the one
you encountered.
If you want to connect to just one beanstalkd instance, use
Beanstalk::Connection.new('0.0.0.0:11300') instead. That will give you
the errors as you would expect.
However, I am not very happy with the original ruby client. This isn't
its only flaw. I recommend checking out http://github.com/dj2/em-jack
instead. It is under more recent active development and it has a
better fundamental architecture (using EventMachine).
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
-~----------~----~----~----~------~----~------~--~---
