kr/beanstalkd — Issue #104: A second connection watching a tube hangs reserve-with-timeout
Author: cpisto
Created: 2012-03-07 19:46:12+00:00
State: open

It seems #78 is still present in 1.5,

If you have two connections watching a tube, both sitting in a reserve-with-timeout, and put a job into the tube (in my case, the ttr is 1800 seconds), the second connection will reserve it and continue operating correctly, the first connection will hang forever and never receive a TIMED_OUT from the server.

In my specific case the client immediately ignores the watched tube after the reserve-with-timeout returns (either with a job or with a timeout), and re-watches it before the next call to reserve-with-timeout.