The Engine Server (oesocketserver.jar) is responsible for responding to requests from outside programs (including OECGI, NetOI, O4W, CTO, AREV32, and more). You may limit the number of OpenEngines that the Engine Server can use for web requests, to manage your license count, by setting MaxEngines in the Engine Server’s configuration file (normally eserver.cfg).

Under certain circumstances, "flooding" the Engine Server with simultaneous requests may cause the number of OpenEngines used to exceed the number specified in MaxEngines. This patch eliminates, or reduces, the chance of this behavior occurring. In addition, it enhances the ability of the Engine Server to remove OpenEngines that are exceeding the maximum run time (as specified in the MaxRunTime setting). Finally, for situations where you wish excessive engine requests to be rejected rather than queued (which is the normal behavior), this Engine Server allows you to specify the startup flags value as a negative value (ie, "-1" or "-65"). A negative startup flag will indicate that, if no open engines are available for the engine server to reuse or create, the request should be rejected; if open engines are available, or new ones can be started, the startup flag is treated the same way as its positive value (ie, "1" or "65").

Please note that the MaxEngines restrictions only apply to "asynchronous" engines, of the sort started by OECGI. "Synchronous" engines, created by CTO, AREV32, and SystemMonitor requests will NOT be limited by the MaxEngines value, and thus the engine server may create up to (MaxEngines + <number of CTO/AREV32 requests> + <number of phantoms> + <number of SystemMonitor processes>) oengines at any one time.

Works Members can download the Engine Server patch HERE.