Hi Hans Thanks for the reply.
I had one jboss instance running and after shutting it down I rebuild and it worked. Great. But still I dont understand how java instance had caused this and what is that that is fixed exactly. It would be really helpful if you shed some more light on this. Thanks once again for the help. On Mon, Apr 19, 2010 at 11:30 PM, Hans Koerber <h...@koerber-net.com> wrote: > Hi Sac, > > I had this (or at least a similar) error a few times and it was usually > another Java instance not ended correctly before starting the app server > again. So you might want to double check that all Java instances are gone > and no 2nd Jetty/Tomcat is running ... > > If I remember correct, at one point it was also related to permissions. But > I'm not sure, though. > > Cheers, > Hans. > > Am Montag, den 19.04.2010, 22:46 +0530 schrieb sac sha: > > Hi All > > I am having problem deploying lenya 2.0 on my tomcat as well as on jetty. > > The build process finishes successfully but when I try to fetch page > of cocoon in browser, it shows initialization error. There is lot of > discussion going on for this on lenya mailing list but I am not able > to find concrete reason and solution for this. > > My logs in log4j is as follows: > > 2010-04-19 22:34:13,105 [main] ERROR core.manager - Caught an > exception trying to initialize the component handler. > org.apache.avalon.framework.configuration.ConfigurationException: > cannot create a quartz scheduler > at > org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:309) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244) > at > org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297) > at > org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108) > at > org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524) > at > org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:583) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244) > at org.apache.cocoon.Cocoon.initialize(Cocoon.java:345) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244) > at > org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1429) > at > org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:499) > at > org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:383) > at > org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:243) > at > org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445) > at > org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:323) > at > org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:511) > at > org.mortbay.jetty.plus.PlusWebAppContext.doStart(PlusWebAppContext.java:149) > at org.mortbay.util.Container.start(Container.java:72) > at org.mortbay.http.HttpServer.doStart(HttpServer.java:753) > at org.mortbay.jetty.plus.Server.doStart(Server.java:153) > at org.mortbay.util.Container.start(Container.java:72) > at org.mortbay.jetty.plus.Server.main(Server.java:202) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at Loader.invokeMain(Unknown Source) > at Loader.run(Unknown Source) > at Loader.main(Unknown Source) > Caused by: org.quartz.SchedulerConfigException: Failure occured during > job recovery. [See nested exception: > org.quartz.JobPersistenceException: Couldn't clean volatile data: > Table not found in statement [SELECT TRIGGER_NAME, TRIGGER_GROUP FROM > QRTZ_TRIGGERS WHERE IS_VOLATILE = ?] [See nested exception: > java.sql.SQLException: Table not found in statement [SELECT > TRIGGER_NAME, TRIGGER_GROUP FROM QRTZ_TRIGGERS WHERE IS_VOLATILE = > ?]]] > at > org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493) > at > org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68) > at > org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:325) > at > org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:269) > at > org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:305) > ... 28 more > 2010-04-19 22:34:13,108 [main] ERROR access - Exception reloading > org.apache.avalon.framework.configuration.ConfigurationException: > cannot create a quartz scheduler > at > org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:309) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244) > at > org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297) > at > org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108) > at > org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524) > at > org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:583) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244) > at org.apache.cocoon.Cocoon.initialize(Cocoon.java:345) > at > org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244) > at > org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1429) > at > org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:499) > at > org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:383) > at > org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:243) > at > org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445) > at > org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:323) > at > org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:511) > at > org.mortbay.jetty.plus.PlusWebAppContext.doStart(PlusWebAppContext.java:149) > at org.mortbay.util.Container.start(Container.java:72) > at org.mortbay.http.HttpServer.doStart(HttpServer.java:753) > at org.mortbay.jetty.plus.Server.doStart(Server.java:153) > at org.mortbay.util.Container.start(Container.java:72) > at org.mortbay.jetty.plus.Server.main(Server.java:202) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at Loader.invokeMain(Unknown Source) > at Loader.run(Unknown Source) > at Loader.main(Unknown Source) > Caused by: org.quartz.SchedulerConfigException: Failure occured during > job recovery. [See nested exception: > org.quartz.JobPersistenceException: Couldn't clean volatile data: > Table not found in statement [SELECT TRIGGER_NAME, TRIGGER_GROUP FROM > QRTZ_TRIGGERS WHERE IS_VOLATILE = ?] [See nested exception: > java.sql.SQLException: Table not found in statement [SELECT > TRIGGER_NAME, TRIGGER_GROUP FROM QRTZ_TRIGGERS WHERE IS_VOLATILE = > ?]]] > at > org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493) > at > org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68) > at > org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:325) > at > org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:269) > at > org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:305) > ... 28 more > > I have already tried clean building lenya and cocoon with java 1.5 and > 1.6. I have tried tomcat version 5.5 and 6.0. > > If I deploy cocoon in externals/cocoon2.1..x only it runs fine. > > Any suggestions will be of great help. > > TIA > > -- Regards Sac --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org For additional commands, e-mail: user-h...@lenya.apache.org
