I can't reproduce it with telnet since I don't know what causes this yet. And it's a critical environment so I'm going to upgrade to 1.4.4 soon. But I'll have a look with Wireshark, thanks for the tip!
On May 11, 9:38 pm, Keith Rarick <[email protected]> wrote: > On Tue, May 11, 2010 at 4:46 AM, Fredrik <[email protected]> wrote: > > When that job is done the job is deleted and the thread returns. This > > call hangs indefinitely at times, even though I can see via other > > connections (telnet) that there are in fact jobs ready to be > > reserved. > > Can you reproduce this with just a single connection in telnet? A > reduced test case will help us track this down much faster. Even if > not, a packet trace will be a huge help. We will know what commands > and responses are being sent, and when. Wireshark is a pretty easy > tool to use if you want to trace network activity. > > 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 > athttp://groups.google.com/group/beanstalk-talk?hl=en. -- 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.
