Hi Thomas,

I am starting a new project with turbine-5.0-SNAPSHOT and I already
updated the web archetype to get the Quartz configuration in place (I
found most of it from the test cases you had in svn).  So far so good...

I added the simplejob test and started it up, however I tried to set it
to run every 10 seconds, but it was only running once per minute - I
don't really need a job to run every 10 seconds, but I thought that was
a little strange. I will have to debug that further.  But the real
reason I am writing is I am trying to understand how to persist the jobs
in the database so they come back on restart.  I first just manually
entered a job in the TURBINE_SCHEDULED_JOB table, but it is not reading
anything from there.

Looking at the startup logs, it says it is using a RAMJobStore store
which is not persistent.  Does the new Quartz scheduler not support
persisting job entries? The log tells me no user-supplied config was
found, so I guess there is some way to configure it further :-)

Once I figure it all out, I was going to put together a simple Job
Manager UI in the flux package similar to the way we have the user
manager.  I think it would be a nice addition (provide basic
functionality, start/stop scheduler, add/remove jobs, check current job
status).  Let me know what you think. 

I need this myself - my new contract I am putting together a system that
allows users to manage a set of keywords and then schedule automated web
crawling to gather relevant data before sending it through some data
mining, text classification processes ;-)

Also, I would be happy to write this all up when I get it working and
add to the site docs (the schedule docs there now only apply to T-2.3.x
version I believe).


Thanks!

Startup is looking good!

2018-10-11 20:15:43,109 [localhost-startStop-1] INFO  avalon.quartz -
Using Quartz default configuration since no user-supplied configuration
was found
2018-10-11 20:15:43,124 [localhost-startStop-1] INFO 
org.quartz.impl.StdSchedulerFactory - Using default implementation for
ThreadExecutor
2018-10-11 20:15:43,127 [localhost-startStop-1] INFO 
org.quartz.simpl.SimpleThreadPool - Job execution threads will use class
loader of thread: localhost-startStop-1
2018-10-11 20:15:43,135 [localhost-startStop-1] INFO 
org.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller
of type: class org.quartz.core.SchedulerSignalerImpl
2018-10-11 20:15:43,136 [localhost-startStop-1] INFO 
org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.3.0 created.
2018-10-11 20:15:43,136 [localhost-startStop-1] INFO 
org.quartz.simpl.RAMJobStore - RAMJobStore initialized.
2018-10-11 20:15:43,137 [localhost-startStop-1] INFO 
org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler
(v2.3.0) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.

2018-10-11 20:15:43,137 [localhost-startStop-1] INFO 
org.quartz.impl.StdSchedulerFactory - Quartz scheduler
'DefaultQuartzScheduler' initialized from default resource file in
Quartz package: 'quartz.properties'
2018-10-11 20:15:43,137 [localhost-startStop-1] INFO 
org.quartz.impl.StdSchedulerFactory - Quartz scheduler version: 2.3.0
2018-10-11 20:15:43,137 [localhost-startStop-1] DEBUG avalon -
Startable.start() for quartz
2018-10-11 20:15:43,137 [localhost-startStop-1] INFO 
org.quartz.core.QuartzScheduler - Scheduler
DefaultQuartzScheduler_$_NON_CLUSTERED started.
2018-10-11 20:15:43,138 [localhost-startStop-1] DEBUG avalon - YAAFI
Avalon Service Container is up and running
.
.
.
2018-10-11 20:15:43,217 [localhost-startStop-1] DEBUG avalon - Located
the service 'org.apache.fulcrum.quartz.QuartzScheduler' in the local
container
2018-10-11 20:15:43,217 [localhost-startStop-1] INFO  scheduler -
Starting job scheduler



--
Jeff


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to