Hey Dave,
after I cleared the table responsible for these jobs,
by setting all dates to 1970 and remove the clientID's
the whole thing started to work again.
I need to keep an eye on it though since I don't understand well
what's going on.
Ries
On Feb 3, 2008, at 10:31 AM, Dave wrote:
When does the error below occur? From the looks of the log messages,
your system is in the process of shutting down. Are there any messages
regarding the HitCountQueueProcessor earlier in the log?
- Dave
On Jan 30, 2008 7:01 PM, ries van Twisk <[EMAIL PROTECTED]> wrote:
I am running roller on tomcat6 with java 1.5 and PostgreSQL.
In my roller log I find the below entry.
INFO 2008-01-31 00:43:51,562 HitCountQueue:shutdown - stopping
worker
HitCountQueueProcessor
INFO 2008-01-31 00:43:51,583 ContinuousWorkerThread:run -
HitCountQueueProcessor Started.
ERROR 2008-01-31 00:43:51,589 WorkerThread:run - Error executing job.
Worker = HitCountQueueProcessor, Job =
org.apache.roller.weblogger.business.runnable.HitCountProcessingJob
java.lang.NullPointerException
at
org.apache.roller.weblogger.business
.runnable.HitCountProcessingJob.execute(HitCountProcessingJob.java:
61)
at
org
.apache
.roller
.weblogger.business.runnable.WorkerThread.run(WorkerThread.java:
68)
at
org
.apache
.roller
.weblogger
.business
.runnable.ContinuousWorkerThread.run(ContinuousWorkerThread.java:76)
INFO 2008-01-31 00:43:51,592 ContinuousWorkerThread:run -
HitCountQueueProcessor INTERRUPT: sleep interrupted
INFO 2008-01-31 00:45:00,253 DatabaseProvider:successMessage -
SUCCESS: Got parameters. Using configuration type JDBC_PROPERTIES
And indeed I don't see my hitcounter changed on a daily base.
I remember somebody had a similar issue, was this resolved? also ,
where
can I check the roller mail archive?
