Bug 113324

Summary: startup initializers sometime run in the wrong order
Product: [Retired] Red Hat Web Application Framework Reporter: Dennis Gregorovic <dgregor>
Component: otherAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-26 22:20:44 UTC Type: ---
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: 106481    

Description Dennis Gregorovic 2004-01-12 16:59:45 UTC 
The initializer classnames in the inits table have no ordering.  So,
the getRuntimeInitializerNames() method in Startup.java lists them in
whatever order the database returns.  This can result is behavior such
as the cms initializer running for the core initializer, which results
in errors.
Comment 1 Dennis Gregorovic 2004-01-15 22:29:51 UTC 
@39423