So I think whatever is causing this is related to the other thread I had opened about the strange timeout behavior, so I'll continue in this thread. I tried telnetting into the server and putting jobs on the queue, and that works as expected. After some debugging, I found that taking out the line:
connection.job = job.Job makes the jobs queue properly, though this also means I don't get the automatic deserialization I think. Seems like a bug in pybeanstalk, or I'm just using this parameter incorrectly somehow. On Dec 4, 6:44 pm, Keith Rarick <[email protected]> wrote: > On Fri, Dec 4, 2009 at 2:57 AM, Saikat Chakrabarti <[email protected]> wrote: > > but my total jobs is increasing every time I submit a job. Does > > beanstalkd automatically discard jobs if no one is listening to the > > tube the job comes in on? > > No, that should not happen. Is it possible that another process is > connected and deleting jobs? What values do you see for > current-connections, current-producers, current-workers, and > current-waiting? > > Can you run a packet trace on the server? That will tell us exactly > what it is being told to do. > > This strengthens the case for a more-carefully-designed debug mode, so > one can get a useful log of server 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 at http://groups.google.com/group/beanstalk-talk?hl=en.
