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

[bugzilla-daemon@ecoinformatics.org]

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


cxh at eecs.berkeley.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|kruland at ku.edu              |




------- Comment #4 from cxh at eecs.berkeley.edu  2007-01-29 08:15 -------
On kepler-dev, Dan wrote:
> Norbert,
>     The problem with multiple instances of Kepler is due to the internal
> database (hsql) used for the cache and keeping track of actors for the
> Kepler  actor list. Running multiple workflows can be done using
> 'momlexecute' or 'ptexecute'. (There are some ant targets for these
> methods in the build.xml file.) These methods avoid even setting up the
> database.
>     Incidently, I disagree with the 'wontfix' decision that Christopher
> quoted for the bug. I think that I should be able to work with multiple
> simultaneous versions of Kepler.
>
> Dan Higgins - NCEAS
>
> Norbert Podhorszki wrote:
> > Hi Christopher,
> >
> > Uhhoh, or what.
> > Then I have to ask that guy, how was he able to execute ten workflows from
> > a script last Fall, since this bug had been resolved a year ago.
> >
> > If you happened to misunderstand me, I clarify now: I do not want to run
> > even one copy of Kepler on a machine. I (may) want to execute two
> > workflows created in Kepler at once on the same machine ;-)
> >
> > Best regards
> > Norbert
> >
> > On Thu, 25 Jan 2007, Christopher Brooks wrote:
> >
> >
> >> Hi Norbert,
> >> See
> >> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2315
> >> is marked as resolved and wontfix.