On Wed Mar 24 19:52:50 +0100 2010, Keith Rarick wrote: > 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.
IIRC, the Java BeanstalkClient automatically maintains thread-local connections. So unless I'm mistaken, the threads do not share the same connection, and that is precisely where this behaviour comes from: RESERVE and DELETE are issued from different connections. So while the job is still reserved by one connection, another connection tries to delete it, which, as expected, results in NOT_FOUND. -- Regards, Andreas -- 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.
