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
The ccm upgrade command does not run the initializers prior to running the Ja...
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
Depends On:
  Show dependency treegraph
Reported: 2004-03-03 10:32 EST by Daniel Berrange
Modified: 2007-04-18 13:03 EDT (History)
0 users

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

Attachments (Terms of Use)

  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

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.