Yes, look in the logging (maybe turn up the loglevel) You'll see a scheduler if it is running. Normally it is a servlet
Indeed! I was missing a timer servlet in my web.xml. Here is how it's initialized:
<servlet> <servlet-name>Scheduler Servlet</servlet-name> <servlet-class>org.jbpm.scheduler.impl.SchedulerServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet>
Any idea why it should be configured as servlet instead of an start-up listener configured through web.xml?:
<listener> <listener-class>xxx.web.StartupListener</listener-class> </listener>
I mean just moving the code from servlet into an application specific start-up listener?
Wondering what is relationship between org.jbpm.scheduler.impl.Scheduler vs org.jbpm.scheduler.db.DbSchedulerService?
We did configure the scheduler service through jbpm.cfg.xml but it doesn't seem to be working (not sure whether spring modules need to kick this off) but now while I was going through this thread, it talks about SchdulerServlet which uses the class org.jbpm.scheduler.impl.Scheduler?
Any clarifications about this confusion?
Thanks for your help.
ok, it is clear now, the Scheduler Servlet is triggering the db.SchedulerSession which is linked to DB Scheduler service.
And how do you do when you don't use web application to start and to use the scheduler and timers ... ?