Rob,
I was having some similar problems getting the turbine scheduler working. I was successful in using the fulcrum scheduler instead. The steps are as follows:
1. In TurbineResources.properties make sure the following lines are entered (or left as is):
#services.SchedulerService.classname=org.apache.turbine.services.schedule.TurbineSchedulerService
scheduler.enabled=false
2. In Fulcrum.properties make sure the following lines are entered/modified:
services.SchedulerService.classname=org.apache.fulcrum.schedule.TurbineSchedulerService
services.SchedulerService.earlyInit=true
3. The Fulcrum scheduler should load jobs off of a database table. It is also supposed to load jobs from within the Fulcrum.properties files. I was unable to get jobs loaded by just entering them in the properties file, so I had to enter them in the database. Turns out that the database table create script was out of date, so I used the attached script to create the table. Then I inserted a record for each job that I wanted to execute. The most import part of the insert was using the entire class name of the job class. Also, your jobs must extend org.apache.fulcrum.schedule.ScheduledJob. The rest of the columns in the table are explained in the documentation.
Also, this link talks about the above steps: http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=467078
Environment:
Turbine 2.2b3
Good luck,
Steve
Steven Kundrot
Perceptive Informatics, Inc.
The information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer.
-----Original Message-----
From: Robert Jose [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 31, 2002 6:06 PM
To: Turbine Users List
Subject: Enabling Scheduler
Hello
I am trying to enable the Turbine Scheduler, but when I change the
scheduler.enabled property in TurbineResources to true, I get the below error.
Does anyone have any ideas as to why?
Thanks
Rob
[Thu Oct 31 14:51:21 PST 2002] -- ERROR --
Exception: org.apache.turbine.services.InitializationException:
TurbineSchedulerService failed to initialize: 'scheduler.enabled' doesn't map to
a Boolean object
Stack Trace follows:
java.lang.ClassCastException: 'scheduler.enabled' doesn't map to a Boolean
object
at
org.apache.commons.configuration.BaseConfiguration.getBoolean(BaseConfiguration.
java:640)
at
org.apache.commons.configuration.BaseConfiguration.getBoolean(BaseConfiguration.
java:598)
at
org.apache.turbine.services.resources.TurbineResourceService.getBoolean(TurbineR
esourceService.java:336)
at
org.apache.turbine.services.resources.TurbineResources.getBoolean(TurbineResourc
es.java:149)
at
org.apache.turbine.services.schedule.TurbineSchedulerService.init(TurbineSchedul
erService.java:114)
rethrown as org.apache.turbine.services.InitializationException:
TurbineSchedulerService failed to initialize: 'scheduler.enabled' doesn't map to
a Boolean object
at
org.apache.turbine.services.schedule.TurbineSchedulerService.init(TurbineSchedul
erService.java:138)
at
org.apache.turbine.services.TurbineBaseService.init(TurbineBaseService.java:108)
at
org.apache.turbine.services.BaseInitableBroker.initClass(BaseInitableBroker.java
:149)
at
org.apache.turbine.services.BaseServiceBroker.doInitService(BaseServiceBroker.ja
va:224)
at
org.apache.turbine.services.BaseServiceBroker.initServices(BaseServiceBroker.jav
a:193)
at org.apache.turbine.Turbine.init(Turbine.java:257)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at
jrun.servlet.WebApplicationService.loadServlet(WebApplicationService.java:1208)
at
jrun.servlet.WebApplicationService.preloadServlets(WebApplicationService.java:76
3)
at jrun.servlet.WebApplicationService.postStart(WebApplicationService.java:258)
at jrun.deployment.DeployerService.initModules(DeployerService.java:711)
at
jrun.deployment.DeployerService.createWatchedDeployment(DeployerService.java:242
)
at jrun.deployment.DeployerService.deploy(DeployerService.java:430)
at jrun.deployment.DeployerService.handleEvent(DeployerService.java:381)
at jrunx.kernel.JRunServiceDeployer.fireEvent(JRunServiceDeployer.java:700)
at
jrunx.kernel.JRunServiceDeployer.deployServices(JRunServiceDeployer.java:111)
at jrunx.kernel.DeploymentService.loadServices(DeploymentService.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at jrunx.kernel.JRun.startServer(JRun.java:483)
at jrunx.kernel.JRun.<init>(JRun.java:401)
at jrunx.kernel.JRun$1.run(JRun.java:258)
at java.security.AccessController.doPrivileged(Native Method)
at jrunx.kernel.JRun.start(JRun.java:255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at jrunx.kernel.JRun.invoke(JRun.java:179)
at jrunx.kernel.JRun.main(JRun.java:167)
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
turbine_scheduler_table.sql
Description: Binary data
turbine_scheduler_table_init.sql
Description: Binary data
-- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
