There is not a different pybeanstalk group. I usually try to reply better to pybeanstalk questions, but I am travelling this week. Sorry about that, I will look more into this when I return home.
On Dec 5, 4:34 pm, Saikat Chakrabarti <[email protected]> wrote: > Sorry for the spam, but I realized that having connection.job = > job.Job on the consumer but not the producer works fine and serializes/ > deserializes correctly into the Job object. The simple_clients.py > example, however, sets connection.job = job.Job for both the producer > and the consumer (and the problem I was having before can be > replicated with simple_clients.py - try just starting it with a > producer and no consumer, then you will see the producer constantly > creating jobs, but if you run a stats on beanstalkd via telnet, none > of these jobs are on the ready queue). So maybe the issue here is > just that the example needs to be fixed? Or is the way the example is > doing it correct, and just the code needs to be fixed to handle a > connection.job = job.Job on the producer side? > > Also, not sure if there is a pybeanstalk group I should be posting > these to instead of here, but I think I've seen Erich posting on here > before, so hoping this reaches him =). > > Thanks, Keith, for helping me out! > > On Dec 5, 11:58 am, Saikat Chakrabarti <[email protected]> wrote: > > > > > 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.
