ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Taylor <saurs...@yahoo.com>
Subject Re: Client calling retired process?
Date Tue, 25 Nov 2008 17:47:39 GMT
Thanks, Alex.  The problem description is a little confusing in this Jira, though.  What
is it that happens, exactly?  

From: Alex Boisvert <boisvert@intalio.com>
To: user@ode.apache.org
Sent: Tuesday, November 25, 2008 11:22:49 AM
Subject: Re: Client calling retired process?

On Tue, Nov 25, 2008 at 9:06 AM, Chris Taylor <saursoor@yahoo.com> wrote:

> In the meantime, this is causing a secondary issue in that when we hit the
> original OOM, we build up a lot of rescheduled jobs (sometimes well over a
> hundred) apparently for requests that cannot be satisfied.  When the server
> starts up again, it immediately pegs at full capacity trying to satisfy
> these.  Other than deleting the rescheduled jobs from ODE_JOB, is there some
> way to change the configuration of ODE to limit how many of these it
> reschedules so as not to back it up?

This was recently fixed on the Ode 1.x branch

but still needs to be ported to the trunk

I'm hoping it will happen in the next week or so.


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