Bug 957691

Summary:	Upgrade Quartz to latest version
Product:	[Other] RHQ Project	Reporter:	Thomas Segismont <tsegismo>
Component:	Core Server	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	962867 (view as bug list)		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	962867

Description Thomas Segismont 2013-04-29 09:20:59 UTC

RHQ ships an old version of Quartz (1.6.5), released on 2009-03-07.

A JON customer recently hit "QUARTZ-774 : Possible hang in SimpleThreadPool.shutdown(true)"

See:
http://web.archive.org/web/20100605021241/http://jira.opensymphony.com/browse/QUARTZ-774

Upgrading Quartz to latest version will bring into RHQ a lot of Quartz fixes.

Comment 2 Thomas Segismont 2013-05-02 13:17:05 UTC

Worth reading:
http://quartz-scheduler.org/documentation/quartz-2.x/new-in-quartz-2
http://quartz-scheduler.org/documentation/quartz-2.1.x/new-in-quartz-2_1
http://quartz-scheduler.org/documentation/quartz-2.1.x/migration-guide

Comment 3 Thomas Segismont 2013-05-02 13:18:13 UTC

From Mazz on rhq-devel on 04/30/2012 at 19:21:
> IIRC, upgrading to the latest quartz would require some of our _QRTZ tables to be upgraded (I think one or more tables in quartz require schema updates).
>
> Just keep that in mind - it will require upgrading testing - and since we use quartz for lots of jobs (either our internal async jobs or jobs to invoke scheduled operations that users define) we have to make sure those jobs/scheduled operations are not broken during the upgrade.
>
> In fact, we'll need to test this EVEN IF there are no schema updates for quartz - we need to make sure the jobs in the _QRTZ tables are forward compatible to be executable in the new quartz.

Comment 4 Thomas Segismont 2013-05-02 13:25:23 UTC

(In reply to comment #3)
> From Mazz on rhq-devel on 04/30/2012 at 19:21:
> > IIRC, upgrading to the latest quartz would require some of our _QRTZ tables to be upgraded (I think one or more tables in quartz require schema updates).
> >
> > Just keep that in mind - it will require upgrading testing - and since we use quartz for lots of jobs (either our internal async jobs or jobs to invoke scheduled operations that users define) we have to make sure those jobs/scheduled operations are not broken during the upgrade.
> >
> > In fact, we'll need to test this EVEN IF there are no schema updates for quartz - we need to make sure the jobs in the _QRTZ tables are forward compatible to be executable in the new quartz.

The Quartz 2.1.x migration guide [1] provides a script for upgrading existing tables. While it needs to be checked as instructions may vary with the database system used, it's a good start.

[1] http://quartz-scheduler.org/documentation/quartz-2.1.x/migration-guide