Bug 957691 - Upgrade Quartz to latest version
Summary: Upgrade Quartz to latest version
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 962867
TreeView+ depends on / blocked
 
Reported: 2013-04-29 09:20 UTC by Thomas Segismont
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 962867 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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 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


Note You need to log in before you can comment on or make changes to this bug.