On 10/15/07, Jonathan Chen <[EMAIL PROTECTED]> wrote:
> I've attached a log snippet below. It looks like the
> ResetHitsCountTask is Launched, but fails to aquire a lease, and then
> when it retries it decides that it can't run and decides to wait until
> next midnight - but that's only an uninformed view. I hope the logs
> can tell you exactly what's happening here.
>
> Cheers.
> --
> Jonathan Chen <[EMAIL PROTECTED]>
>
> --- Roller debug log ---
> DEBUG 2007-10-16 00:00:00,050 GeronimoLog:debug - Current time = Tue
> Oct 16 00:00:00 NZDT 2007
> DEBUG 2007-10-16 00:00:00,052 GeronimoLog:debug - Started - Tue Oct 16
> 00:00:00 NZDT 2007
> DEBUG 2007-10-16 00:00:00,055 GeronimoLog:debug -
> ScheduledEntriesTask: next allowed run time = Sat Sep 29 17:11:00 NZST
> 2007
> DEBUG 2007-10-16 00:00:00,056 GeronimoLog:debug - MISSED last run,
> checking if waiting is necessary
> DEBUG 2007-10-16 00:00:00,056 GeronimoLog:debug -
> ScheduledEntriesTask: LAUNCHING task
> DEBUG 2007-10-16 00:00:00,058 GeronimoLog:debug -
> ScheduledEntriesTask: Attempting to acquire lease
> DEBUG 2007-10-16 00:00:00,066 GeronimoLog:debug -
> ScheduledEntriesTask: Lease NOT acquired, cannot continue

I'm not having any problem with my reset hits and turn-over referrers
tasks. Unfortunately, I don't have much experience with the new task
management system. I suppose it is possible that your task-lock table
has become inconsistent -- so you might want to try stopping Roller,
clearing the roller_tasklock table and then restarting.

Also, how do you have your tasks configured? Are you using the default
start times and intervals?

And, do you know if this behavior exists on Tomcat too, or just Geronimo?

- Dave

Reply via email to