Closed zeeshan-v1 closed 7 years ago
Can this be reproduced with another Quartz store? So far there is no evidence that it is an issue in the store.
I havent checked with Quartz RamJobStore yet, will do and update. One thing i wanted to mention is i havent added below line in props- is that going to cause an issue?
org.quartz.jobStore.jobDataAsBase64=false
I also tried the Job with Non-Durability as well, the issue persists. Whatever i add with usingJobData on Trigger is not being transferred to Job Instance
org.quartz.jobStore.class=com.novemberain.quartz.mongodb.MongoDBJobStore org.quartz.jobStore.mongoUri=mongodb://localhost:27017 org.quartz.jobStore.dbName=mailemergencydb2 org.quartz.jobStore.collectionPrefix=mailemergency org.quartz.threadPool.threadCount=1 org.quartz.scheduler.instanceName = MailEmergencyJobScheduler org.quartz.scheduler.skipUpdateCheck=true
FIXED by using correct version of Jar. I was using quartz-mongodb-2.0.0-rc2.jar where as i should have been using quartz-mongodb-2.0.0.jar
http://stackoverflow.com/q/42025607/3148412
I have a durable job added to the scheduler. At the runtime, i am building a trigger using below code:
I then schedule this job using ,
scheduler.scheduleJob(trigger);
The job is executed properly, however the Jobdata ("test" string param) is giving me null in the job. this is my job code,