[kepler-dev] [Bug 5444] Kepler can't run workflow if two instances exist at same time

[bugzilla-daemon at ecoinformatics.org]

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

--- Comment #7 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-08-08 14:21:22 PDT ---
In r28216 Dan added a way to start the hsql servers using kepler.sh -hsql start
and kepler.sh -hsql stop. This allows multiple instances of kepler to start and
stop successfully; you first run kepler.sh -hsql start, run and quit as many
instances of kepler as you like, and then shutdown the servers with kepler.sh
-hsql stop. (Note this does not solve the issue of databases being shared
between users on the same machine bug#5278).

This isn't an ideal solution for users, but it's a workable solution for our
needs with the scheduler. 
For users, ideally the first kepler starts the servers, and the last running at
any given time stops them. This will either require checking the databases for
open connections, or keeping a shared, properly locked list of all running
keplers that each kepler updates on start and quit.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.