Greetings all, Thanks for all of your efforts to make this such a fantastic library! It is proving quite useful in my project.
I have a question regarding queuing tasks and the bdrb_job_queues database. I am working with a feed validator. I am passing the job of validating and updating requested feeds to backgroundrb using the following line: worker = MiddleMan.worker(:validate_feeds_worker).enq_validate_feeds(:arg => feed_ids_to_validate, :job_key => job_key) Everything works great for a while, but if I leave it alone, it eventually stops processing. One of the things I have noticed is that in the database, the `taken` field is switched to '1' (true) but the fields for `finished` and `finished_at` are never populated. Would this have something to do with the problem? I operated on the assumption that the cause could lie in my worker processes. The worker basically finds the Feed model requested and then calls the validate_feed method on the Feed model. The rest of the code sits in the Model and a module. I have thoroughly tested and evaluated my algorithm and can find no cause or problems with the code. It all works as expected when left to its own devices or called in a simple state against a single feed. I would be very grateful if anyone could point me in the right direction to remedy this problem. It is the main challenge preventing us from finishing a project that has been in development for quite some time and we are all chomping at the bit! -- Jay Sanders http://mindtonic.net
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
