Adam, that's great news and thanks for the feedback. I guess we should consider changing the name of our properties so that it doesn't happen again.
http://www.tomitribe.com - @AndyGeeDe - On a mobile device, and I have fat fingers. Sorry for typos. On 21 Oct 2014 07:58, "Adam Steen" <[email protected]> wrote: > Hi > > I figure out quartz is trying to load the quartz.properties file from > apache-tomee-plus-1.7.1/lib/quartz-openejb-shade-2.2.1.jar!/quartz.properties, > as that’s the first properties file on the class path. > > I have solved the problem, but just renaming the quartz.properties we use > to something else, and problem solved. > > Regards, > > Adam Steen | Software Developer > Risk Management Technologies | Tel: +61 8 9322 1711 > > -----Original Message----- > From: Adam Steen [mailto:[email protected]] > Sent: Tuesday, 21 October 2014 8:05 AM > To: [email protected] > Subject: RE: Legacy Quartz and Tomee 1.7.1+ > > Hi Romain > > We use 1.1.6, which is why we don’t have the setter. > > Regards, > > Adam Steen | Software Developer > Risk Management Technologies | Tel: +61 8 9322 1711 > > -----Original Message----- > From: Romain Manni-Bucau [mailto:[email protected]] > Sent: Monday, 20 October 2014 5:26 PM > To: [email protected] > Subject: Re: Legacy Quartz and Tomee 1.7.1+ > > Hi > > we don't have org.quartz packages anymore, which version do you use? > quartz 1.5 has the setter. > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2014-10-20 11:16 GMT+02:00 Adam Steen <[email protected]>: > > Hi > > > > I was previously using Tomee 1.5.2 for our WebApp and was able to > successful use a legacy version of quartz alongside whatever version Tomee > 1.5.2 was using. > > > > I have downloaded Tomee 1.7.1 Plus and was pleasantly surprised our app > just ran out of the box, my joy was short lived when I tried to access some > legacy information through the older version of Quartz. > > > > I would have thought adding "openejb.classloader.forced-load=org.quartz" > to my system.properties but I still get the following exception when try to > access the Scheduler for the first time. > > > > Exception: ThreadPool class 'org.quartz.simpl.SimpleThreadPool' props > could not be configured. > > <snip> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) > > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) > > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > > at > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) > > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) > > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) > > at > org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) > > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) > > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) > > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) > > at > org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:312) > > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) > > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > > at > org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070) > > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611) > > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > > at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > > at java.lang.Thread.run(Thread.java:745) > > Caused by: org.quartz.SchedulerException: ThreadPool class > > 'org.quartz.simpl.SimpleThreadPool' props could not be configured. [See > nested exception: java.lang.NoSuchMethodException: No setter for property > 'threadsInheritContextClassLoa derOfInitializingThread'] > > at > org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:462) > > at > > org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.j > > ava:827) > > > > My quartz.properties file > > > > <snip> > > > > org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool > > org.quartz.threadPool.threadCount = 3 > > org.quartz.threadPool.threadPriority = 4 > > > > <snip> > > > > org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreCMT > > org.quartz.jobStore.driverDelegateClass = > > au.com.rmt.scheduler.jdbcjobstore.oracle.RMTOracleDelegate > > org.quartz.jobStore.dataSource = oracle > > org.quartz.jobStore.tablePrefix = QRTZ_ org.quartz.jobStore.instanceId > > = 1 > > > > <snip> > > > > I have tried a number of things with no success, and google has been any > help either, any ideas where to check next? > > > > Regards, > > > > Adam Steen > > >
