On Tue, Mar 23, 2010 at 1:07 PM, Andreas Bolka <[email protected]> wrote: > On Tue Mar 23 19:38:52 +0100 2010, tcn wrote: >> I don't get it, can somebody explain what I am doing wrong? > > You try to delete a job which is not in the tube. This happens, because
It looks like all the threads are sharing the same connection. This suggests a race condition. It's a little surprising the reserve commands even worked. To get this working with minimal changes, you'll have to put some synchronization around the client variable. Better yet, don't share state between threads. Instead try a different concurrency model. For beanstalkd workers, people often use a collection of single-threaded processes. 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.
