Bug 117390 – The ccm upgrade command does not run the initializers prior to running the Java upgrade

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 117390 - The ccm upgrade command does not run the initializers prior to running the Java upgrade

Summary:	The ccm upgrade command does not run the initializers prior to running the Ja...

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Web Application Framework
Classification:	Retired
Component:	installation (Show other bugs)
Sub Component:
Version:	nightly
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	ccm-bugs-list
QA Contact:	Jon Orris
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-03-03 10:32 EST by Daniel Berrange
Modified:	2007-04-18 13:03 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-09-02 13:35:18 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Berrange 2004-03-03 10:32:46 EST

Description of problem:
The ccm load command ensures that all dependant Initializers have been
run prior to invoking the 'run(ScriptContext)' method on the loader.
This is not done when running the 'ccm upgrade' command, which means
any attempt to use system services, in particular, persistence fail.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run a Java upgrade scripts

Actual results:
No initializers are run & errors are thrown when trying to use
persistence.

Expected results:
All initializers are run.

Additional info:

Comment 1 Justin Ross 2004-03-03 13:46:05 EST

The current pattern is to invoke the main method of some named Java
code, and I left the burden with that code to do a "new Startup().run()".

This allows upgrades to be run via ccm-run just as they are from ccm
upgrade.  That is, you can use ccm upgrade -f 6.0 -t 6.1 or you can

  $ ccm-run com.arsdigita.cms.RickshawPublishAPIUpgrade

if you prefer.  Some upgrades may not need initialization.

I can definitely changing this, but if we did I'd want to introduce an
interface and define a richer contract for Java upgrades viz CCM.

Comment 2 Daniel Berrange 2006-09-02 13:35:18 EDT

Closing old tickets

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