configuring Quartz scheduler in tomcat 6 using JNDI

[Shantanu Puranik]

Hello,

I'm working on project that involves porting legacy app. from old version of JBoss and java to tomcat 6.x and jdk 1.6.
Quartz 1.6 is configured as JNDI resource using mbean in old app.
For new app. Quartz version remains the same.

What I 've done till now:
1. Created myWebApp_quartz.properties file and placed under /webapps/myWebApp/WEB-INF/classes

org.quartz.scheduler.instanceName = myWebAppQuartz
org.quartz.scheduler.rmi.export = false
org.quartz.scheduler.rmi.registryPort = 4711
org.quartz.scheduler.rmi.createRegistry = false
org.quartz.scheduler.rmi.proxy = false
org.quartz.scheduler.xaTransacted = false
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 5
org.quartz.threadPool.threadPriority = 4
org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore
org.quartz.jobStore.misfireThreshold = 60000

2. Added following entry in web.xml

<servlet>
	    <servlet-name>
	        QuartzInitializer
	    </servlet-name>

	    <display-name>
	       Quartz Initializer Servlet
	    </display-name>

	    <servlet-class>
	        org.quartz.ee.servlet.QuartzInitializerServlet
	    </servlet-class>

	    <init-param>
	        <param-name>config-file</param-name>
	        <param-value>C:/apache-tomcat-6.0.24/webapps/myWebApp/WEB-INF/classes/myWebApp_quartz.properties</param-value>

	    </init-param>

	    <init-param>
	        <param-name>shutdown-on-unload</param-name>
	        <param-value>true</param-value>
	    </init-param>

	    <init-param>
	        <param-name>start-scheduler-on-load</param-name>
	        <param-value>true</param-value>

	    </init-param>

	    <load-on-startup>
	         1
	    </load-on-startup>
</servlet>

I get an exception saying, javax.naming.NameNotFoundException: Name myWebAppQuartz is not bound in this Context
It means that quartz instance isn't registered with JNDI.
I want to know how to configure Quartz scheduler in tomcat 6 using JNDI.
Thank you.

[Shantanu Puranik]

Just figured out with help of tomcat help resource
Scroll down the page to section Adding Custom Resource Factories

1. Implement interface javax.naming.spi.ObjectFactory

package com.myWebApp.quartz;

import java.util.Hashtable;

import javax.naming.Context;
import javax.naming.Name;
import javax.naming.spi.ObjectFactory;

import org.apache.commons.logging.Log;
import org.quartz.Scheduler;
import org.quartz.impl.StdSchedulerFactory;


public class MyQuartzSchedulerFactory implements ObjectFactory {

		public Object getObjectInstance(Object arg0, Name arg1, Context arg2,
			Hashtable<?, ?> arg3) throws Exception {

		// Acquire an instance of our specified bean class
		StdSchedulerFactory ssf = new StdSchedulerFactory("quartz.properties");
		Scheduler myQuartzScheduler = ssf.getScheduler();
// Return the customized instance
	      return (myQuartzScheduler);


	}

}

2. create quartz.properties file as shown in the above post (consider specifying additional properties as required by your app.)

3. In web.xml add resource ref

<resource-ref>
	  <res-ref-name>myWebAppQuartz</res-ref-name>
	  <res-ref-type>org.quartz.Scheduler</res-ref-type>
	  <res-auth>Container</res-auth>
</resource-ref>

4. create context.xml in the project structure at location /webapps/META-INF.
When deployed tomcat will automatically create <myWebApp>.xml in dir. \tomcat\conf\Catalina\localhost and the contents of context.xml will be copied into it.

<Context path="/myWebApp">
  <Resource name="myWebAppQuartz" auth="Container"
            type="org.quartz.Scheduler"
            factory="com.myWebApp.quartz.MyQuartzSchedulerFactory"
            />
</Context>

Finally, perform lookup as

try {
			InitialContext ic = new InitialContext();
			Context envCtx = (Context) ic.lookup("java:comp/env");
			Scheduler sch = (Scheduler) envCtx.lookup("myWebAppQuartz");
			
		} catch( NamingException e ) {
			e.printStackTrace();
		} catch (SchedulerException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}