Bug 113324 - startup initializers sometime run in the wrong order
startup initializers sometime run in the wrong order
Status: CLOSED RAWHIDE
Product: Red Hat Web Application Framework
Classification: Retired
Component: other (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dennis Gregorovic
Jon Orris
:
Depends On:
Blocks: 106481
  Show dependency treegraph
 
Reported: 2004-01-12 11:59 EST by Dennis Gregorovic
Modified: 2007-04-18 13:01 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-01-26 17:20:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dennis Gregorovic 2004-01-12 11:59:45 EST
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 17:29:51 EST
@39423

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