Dear Beanstalkd Benefactors, I love beanstalkd, thank you so much for providing this!
I got stuck for a while in trying to set up use of beanstalkd to process a queue of after_commit actions in Rails. I mistook my problem as being Rails' ActiveRecord not being able to find the record I had just committed, despite the fact that I was putting it into the pipe using after_commit. Of course, I spend lots of time making sure I was using after_commit correctly -- this was just the type of symptom which would occur if I was putting the request into the pipe from the Controller, or was using the wrong callback in ActiveRecord. It turned out my problem was misuse of the beaneater automatic processing protocol. I was calling job.delete at the end of the method registered to process a job. I think my job.delete worked, but left beaneater getting a NOT_FOUND error when it went to delete the job as well, which I mistook for a NOT_FOUND from my database lookup of the record in process. So, this is me sharing my stupid mistake, hoping it will help someone else. And, I would point out that if the error was BEANSTALKD_JOB_NOT_FOUND or some such, I would have gotten onto the right track more quickly. Thanks again for sharing a great product. -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/d/optout.
