You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Jürgen Hoffmann <jh...@byteaction.de> on 2002/09/02 11:57:58 UTC
fulcrum
Hi,
Opposed to the opinion of people on this list the problem with the
fulcrum scheduler has not been solved, and since the developers of the
Fulcrum Scheduler must be on vacation, or their machines fell apart,
since they do not answer emails, I am sending this message to the list
=)
I have one big problem to get the fulcrum scheduler up and running. The
fulcrum howto located at the website does not work. Fulcrum inittializes
correctly and gets loaded as a component from the ComponentService.
Here is the log extract:
[Fri Aug 30 13:25:29 CEST 2002] -- DEBUG -- Fixing up
/WEB-INF/conf/Fulcrum.properties [Fri Aug 30 13:25:29 CEST 2002] --
DEBUG -- Now:
/home/saso/tdk-2.2-b3/webapps/contentanalysis/WEB-INF/conf/Fulcrum.prope
rties
[Fri Aug 30 13:25:29 CEST 2002] -- INFO -- Added fulcrum as a component
Fulcrum.properties has the following entries:
services.SchedulerService.classname=org.apache.fulcrum.schedule.TurbineS
chedulerService
services.SchedulerService.earlyInit = true
But I cannot find any logentry that the SchedulerService has started. If
I place the lines into TR.props as stated in the Howto I get the
following error:
services.SchedulerService.classname=org.apache.fulcrum.schedule.TurbineS
chedulerService (Entry in TR.props)
[Fri Aug 30 13:19:23 CEST 2002] -- ERROR --
Exception: org.apache.turbine.services.InstantiationException:
Failed to instantiate service SchedulerService
Stack Trace follows:
java.lang.ClassCastException:
org.apache.fulcrum.schedule.TurbineSchedulerService
at
org.apache.turbine.services.BaseInitableBroker.getInitableInstance(BaseI
nitableBroker.java:257)
rethrown as org.apache.turbine.services.InstantiationException: Class
org.apache.fulcrum.schedule.TurbineSchedulerService doesn't implement
Initable.
at
org.apache.turbine.services.BaseInitableBroker.getInitableInstance(BaseI
nitableBroker.java:295)
at
org.apache.turbine.services.BaseServiceBroker.getServiceInstance(BaseSer
viceBroker.java:359)
rethrown as org.apache.turbine.services.InstantiationException: Failed
to instantiate service SchedulerService
at
org.apache.turbine.services.BaseServiceBroker.getServiceInstance(BaseSer
viceBroker.java:369)
In TR.props I set scheduler.enabled = true of course.
What to do? Where to look for misconfigurations?
Config in TR.props lokks like this:
services.ComponentService.name = fulcrum
services.ComponentService.fulcrum.classname = org.apache.fulcrum.Fulcrum
services.ComponentService.fulcrum.config =
/WEB-INF/conf/Fulcrum.properties
Kind regards
Jürgen Hoffmann
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>