ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: Client calling retired process?
Date Wed, 26 Nov 2008 01:07:53 GMT
On Tue, Nov 25, 2008 at 2:01 PM, Chris Taylor <saursoor@yahoo.com> wrote:

> Incidentally, in analyzing this issue it would seem that the process store
> was holding multiple "Active" versions of the same process (so, multiple
> PIDs of the same Type in the STORE_PROCESS were Active at the same time).
> I wonder if this development environment, wherein we are using the
> DeploymentService to deploy Deployment Units (and thus versioned deployment
> directories), combined with a couple different deployments of the ODE
> runtime engine was causing these "logically" retired processes to hang
> around as Active.
> Going out on a limb here, but does it make sense during times of recovery
> that the engine might get confused about which process Type to route to if
> there were multiple Active Process IDs of it at the same time?

I think that's entirely possible.   Matthieu could confirm since he's more
familiar with that part of the code.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message