Strange Engine (OpenInsight 32-bit)
At 17 JAN 2012 04:52:39PM cborne wrote:
What does this mean when an engine does not have an Engine Status or Requests received? This engine was spawned by OECGI on the web server.
At 18 JAN 2012 08:45AM Jared Bratu wrote:
The engine may have encountered a problem launching which prevented it from properly starting up. In that state shown it maybe be unable to respond to the windows close request when the calling OECGI thread ended.
Check your IIS logs, do you have requests that exceeded the CGI maximum execution time?
Does your application frequently (one engine every second or two) create and destroy OpenEngine instances?
Lastly, if you check the thread with SysInternals Process Explorer what activity does the "Threads" tab indicate for that process?
This isn't a widely experienced problem but there have been some important changes to the start up routine to resolve engine launch problems. One change that comes to mind resolved a problem with engines that took longer than 5 seconds to launch into the users repository application. Because all engines are created with SYSPROG and then swap to the users repository application the background indexer was running before the users application had a chance to establish it's environment.
At 18 JAN 2012 11:15PM cborne wrote:
The engines that are spawned by OECGI are open for 15 minutes before they are destroyed.
I did not see anything that exceeded the CGI maximum execution time.
Where do I check the thread with SysInternals Process Explorer?
I have only seen the maybe 3 times, I just happened to catch it - so I figured I would ask what it could mean. It was not degrading performance or anything. Just curious really. Thanks!
At 19 JAN 2012 01:07AM bshumsky wrote:
The engines that are spawned by OECGI are open for 15 minutes before they are destroyed.
I did not see anything that exceeded the CGI maximum execution time.
Where do I check the thread with SysInternals Process Explorer?
I have only seen the maybe 3 times, I just happened to catch it - so I figured I would ask what it could mean. It was not degrading performance or anything. Just curious really. Thanks!
Just to clarify - are you talking about OECGI (as you stated in your posts), or OECGI2 or OECGI3? The behavior of OECGI is very different than OECGI2/OECGI3, and I'd like to make sure we're all talking about the same thing.
Thanks!
- Bryan Shumsky
At 19 JAN 2012 07:32AM cborne wrote:
Sorry, OECGI2.