On 11/6/07, Lee Fyock <[EMAIL PROTECTED]> wrote: > > Excellent, thanks very much. > > I'm completely baffled by the behavior I'm seeing. I have a small > Rails app that is responsible for scheduling tasks. It has a couple of > controller methods so other web applications can call it to schedule > items, which are simply URLs for the scheduler application to call at > the appropriate time. That works well. > > Now, occasionally I'd like to unschedule a schedule_every item. My > plan was to tag the item, so that I could unschedule it by tag. > However, I can't find the item, despite its continuing to fire. I > backed out the tagging, and I'm still seeing the same behavior -- the > scheduled job can't be found via pending_jobs or cron_jobs (or via job > ID), but it continues to fire. > > If I add another job to the scheduler, then suddenly both jobs show up > in a traversal of pending_jobs, but only immediately after the > schedule_every of the second job. The next time the scheduler fires, > only the second job shows up. (I have a routine that dumps > pending_jobs and cron_jobs via logger when the scheduler fires, or > when I schedule items.) > > Any ideas on how to debug this?
A reduced test case that shows the faulty behaviour would be great. Meanwhile, I will focus on adding test for unscheduling 'schedule_every' jobs. What's the frequency of your ghosty schedule every job ? Thanks for the feedback, I will start investigating with the info given here. Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" 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/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
