[kepler-dev] [Bug 2315] - Unable to run multiple Kepler instances simultaneously

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2315





------- Comment #11 from leinfelder at nceas.ucsb.edu  2009-03-06 15:09 -------
good point about closing the first Kepler - the db server would die with it.
Now I've got it so that the server starts up if need be when a connecting is
requested - so if the first Kepler is terminated (and the hsql server with it)
the second Kepler can then start up the server when a connection is needed.
BUT: I had to refactor some of the CacheManager class (and a few others) so
that there is no DBConnection member variable (otherwise the conn that is
originally made when the object is instantiated can become "broken" when the
server's JVM switches. It means more calls to getDBConnection() (and also
conn.close()) - but I think that should be alright.