Very well. Sync with git master and send me anything you have in debug log file.
On Wed, Apr 29, 2009 at 2:33 AM, Jay Sanders <[email protected]> wrote: > Thanks for taking the time to help me! > > My worker code is here: > > # must be called with > MiddleMan(:validate_feeds_worker).enq_validate_console_feeds(:arg => > feed_ids_array,:job_key => "Item Id") > def validate_console_feeds(feeds) > logger.info 'Starting the feed validator' > i = 1 > feeds.each do |feed_id| > f = Feed.find(feed_id) > f.update_feed > percent_complete = ((i + 1) * 100) / feeds.length > logger.info("#{percent_complete}% Complete - Validating feed > #{feed_id}: #{f.address} (#{f.status})") > i += 1 > end > logger.info 'Finished!' > persistent_job.finish! > end > > > Obviously the `update_feed` method is the bulk of the job. It is located > in a module, and every step of the way has rescues and such to keep it from > breaking down. > > I am using: > > Rails 2.3.2 > backgroundrb: I'm not sure which version, I don't see a version number in > the source code > Packet 0.1.14 > > > > > On Tue, Apr 28, 2009 at 12:59 PM, hemant <[email protected]> wrote: > >> When a job is done, you need to call: >> >> persistent_job.finish! >> >> And that should mark as job done in the database table as well. As for >> your problem, it looks like the worker is stalled at processing some job. >> Can you post your worker code? Also which your app is running with which >> version of rails and which version of backgroundrb plugin and packet gem you >> are using. >> >> >> >> On Tue, Apr 28, 2009 at 10:03 PM, Jay Sanders <[email protected]>wrote: >> >>> 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 >>> >> >> >> >> -- >> Let them talk of their oriental summer climes of everlasting >> conservatories; give me the privilege of making my own summer with my own >> coals. >> >> http://gnufied.org >> > > > > -- > Jay Sanders > http://mindtonic.net > -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
