[jboss-jira] [JBoss JIRA] Resolved: (JBAS-3640) Clustering of the quartz-ra.rar failes
Weston Price (JIRA)
jira-events at jboss.com
Tue Sep 19 10:00:01 EDT 2006
[ http://jira.jboss.com/jira/browse/JBAS-3640?page=all ]
Weston Price resolved JBAS-3640.
--------------------------------
Fix Version/s: JBossAS-4.0.5.GA
Resolution: Done
Simple fix for volatility property discrepancy. Also added durable and recoverable flags to the QuartzActivationSpec.
> Clustering of the quartz-ra.rar failes
> --------------------------------------
>
> Key: JBAS-3640
> URL: http://jira.jboss.com/jira/browse/JBAS-3640
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-4.0.4.GA
> Environment: Clustered JBoss where the Quartz-ra.rar is set up for clustering by using any JDBC DataStore
> Reporter: Kerry Barnes
> Assigned To: Weston Price
> Fix For: JBossAS-4.0.5.GA
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list