• Bug
  • Status: Resolved
  • 2 Major
  • Resolution: As Designed
  • drb
  • Reporter: klalithr
  • October 11, 2012
  • 0
  • Watchers: 4
  • October 15, 2012
  • October 15, 2012



It seems like only the job map entries that are put into the JobDataMap before adding the job to the JobScheduler are preserved across the client/server boundary.

I am not sure of customers Quartz version used. I have requested that info.


James House 2012-10-15

That’s always true, for any job store, and not just for RMI client/server use cases. (Even for 100% local).

If you change a job/trigger, you must re-store it if you want the scheduler to know about it.

Fiona OShea 2012-10-15

Can we add this to FAQ? It comes up quite often.