Client.reserve does not block (with any timeoutSeconds value)

[newobj]

 Job job = client.reserve(3600);

returns immediately with a null job when the watched tubes are empty. Is this expected?

using the 1.0.4 code in Downloads.

[newobj]

I'm actually wondering if this is a problem with my server. If I telnet straight to beanstalkd and type "reserve-with-timeout 3600" it returns immediately with "TIMED_OUT". If I type "reserve-with-timeout 4500" it hangs indefinitely. Ahh, that's pretty weird, wouldn't you say?

[RTykulsker]

Wow, you waited 4500 seconds (75 minutes) and it hung?

Yes, weird. I do have an explicit test for reserve-with-timeout on an empty tube. I'll try to look at this tonight.

[RTykulsker]

I can't reproduce ...