Fedora startup failed
fedora.server.errors.ModuleInitializationException: A connection pool could
not
be instantiated. The underlying error was a
java.lang.NumberFormatExceptionThe
message was "null".
at
fedora.server.storage.ConnectionPoolManagerImpl.initModule(ConnectionPoolManagerImpl.java:214)
at fedora.server.Module.<init>(Module.java:48)
at
fedora.server.storage.ConnectionPoolManagerImpl.<init>(ConnectionPoolManagerImpl.java:69)
------- Additional Comment #1 From Chris Wilper 2007-01-23 12:49 [reply]
-------
CAUSE:
------
This is caused by a badly-populated fedora.fcfg at install-time. Due to
the use
of different case when auto-populating the initial fedora.fcfg, the
installer
ends up creating a partially-populated "datastore" element named
"localPostgresqlPool" (vs. "localPostgreSQLPool"). This ultimately causes
the
NumberFormatException at startup because the ConnectionPoolManager module
expects a numeric param value that isn't present for
"localPostgresqlPool".
WORKAROUND:
-----------
Users can work around this problem by taking the following steps:
1) After running the installer, open the file
$FEDORA_HOME/server/config/fedora.fcfg in an editor.
2) Find the datastore with id="localPostgreSQLPool" (uppercase SQL).
3) Copy all "param" elements EXCEPT the first four (dbUsername,
dbPassword,
jdbcURL, jdbcDriverClass)
4) Go to the end of the file, into the datastore with
id="localPostgresqlPool"
(lowercase sql) and paste the copied "param" elements after the four
existing
elements.
5) You can now remove the entire, old datastore element with
id="localPostgreSQLPool" (uppercase SQL).
6) Save the modified fedora.fcfg.
7) Start Fedora as usual.
