We thought there was a configuration option in eserver.cfg that will force the OEngine Server to close engines after running for so many minutes, but we can't find any documentation or examples for this. Is there anything like this?

We have a system that tends to lose connection to the OI server and were hoping to see if closing the engines automatically and restarting them will help the system stay running.

Don Bakke

SRP Computer Solutions, Inc.

We thought there was a configuration option in eserver.cfg that will force the OEngine Server to close engines after running for so many minutes, but we can't find any documentation or examples for this. Is there anything like this?

We have a system that tends to lose connection to the OI server and were hoping to see if closing the engines automatically and restarting them will help the system stay running.

Don Bakke

SRP Computer Solutions, Inc.

Hi, Don. There are available settings for MaxRunTime and MaxUpTime. MaxRunTime is the maximum amount of time that an oengine is allowed to process a particular request - this is to try and fix "infinite loops", for example. MaxUpTime is the maximum amount of time that a particular engine can be kept "alive", whether it's running or in the "waiting to be reused" queue. So perhaps setting MaxUpTime to some value (I believe the value is the number of minutes) might give you the behavior you're looking for?

Hope that helps,

- Bryan Shumsky

Revelation Software, Inc.

Hi, Bryan. Yes, I think MaxUpTime is closer to what I am looking for. Please clarify something for me. Will this cause an engine to be closed when actively processing a request or will it was for it to finish?

Don Bakke

SRP Computer Solutions, Inc.

Hi, Bryan. Yes, I think MaxUpTime is closer to what I am looking for. Please clarify something for me. Will this cause an engine to be closed when actively processing a request or will it was for it to finish?

Don Bakke

SRP Computer Solutions, Inc.

Hi, Don. It looks like the code will try to close an oEngine that has exceeded the maxUpTime minutes when it's "checked in" after being active, or if it's in the "available to be reused" queue, so it will NOT be closed when actively processing a request.

This is different from the behavior of maxRunTime, which (by definition) will try to kill the oEngine when it's been actively processing after <maxRunTime> minutes.

Hope that helps,

- Bryan Shumsky

Revelation Software, Inc.

View this thread on the Works forum...