On 9/28/06, Peter Petersson wrote: > Yes I could try it out on my devel maskin and if it helps I will > probably upgrade the server maskin(s). > But before I try that, as I can correct the problem by editing the > config.xml is there a way to make the > config stay correct ? If I remember the bug correctly, you may be able to work around the problem by providing the groupId, artifactId, and version elements in addition to the name element. Those should hold the group, artifact, and version of the module that holds the thing you're referencing -- in this case, the module that holds the thread pool (which I think is in geronimo/rmi-naming/1.1/car). If that doesn't work, you may just have to upgrade. Thanks, Aaron > Aaron Mulder skrev: > > There was a bug fixed in Geronimo 1.1.1 that definitely seems related > > -- but I wasn't aware that it struck if you just ran the server with a > > plugin like that. Anyway, is it an option for you to upgrade to > > 1.1.1? > > > > Thanks, > > Aaron > > > > On 9/27/06, Peter Petersson wrote: > >> Hi all! > >> > >> I use Geronimo 1.1 and have installed the QuartzScheduler and > >> QuartzDeployer pluggins and it works fine until i restart the server. > >> The Geronimo server fails to start due to a configuration error for > >> QuartzScheduler in ${GERONIMO_HOME}/var/config/config.xml > >> I have found the problem to be the marked line below > >> > >> > >> > >> >> name="quartzProperties">org.quartz.threadPool.class=org.gplugins.quartz.QuartzThreadPool > >> > >> > >> org.quartz.scheduler.jobFactory.class=org.gplugins.quartz.QuartzJobFactory > >> > >> > >> <<<<<<<<<<<<<<<<========================== > >> > >> > >> > >> > >> When I "correct" it and starts the server with > >> > >> > >> > >> >> name="quartzProperties">org.quartz.threadPool.class=org.gplugins.quartz.QuartzThreadPool > >> > >> > >> org.quartz.scheduler.jobFactory.class=org.gplugins.quartz.QuartzJobFactory > >> > >> > >> > >> DefaultThreadPool > >> > >> > >> > >> > >> > >> It works fine until the next time I stop and start the server as the > >> config.xml file is regenerated with the error. > >> > >> What can I do to fix the problem (permanently)? > >> > >> Cheers > >> Peter > >> >