Clustering of the quartz-ra.rar failes

When using a JDBC Data Store for the Quarts-ra.rar, the rar fails by indicating that you cannot have a non-volatile trigger associated with a volatile job.

The JobStoreCMT file checks to make sure that if the JobDetail is marked as "volatile" the corresponding Trigger is also marked as "volatile." But, in the QuartzResourceAdapter.java the JobDetail is created with a volatility set to "true" during construction, but the CronTrigger doesn't supply that option at construction and the default setting is to have the volatility set to "false," which is never changed. A mismatch and a problem

The easiest solution is to modify the JobDetail construction volatility parameter to false so that both instances match. In my tests this generates the desired effect.