RE: [Webware-devel] monitor.py usage?

[Geoffrey T. <gta...@na...>]

Stuart Donaldson [mailto:st...@al...] wrote:
> So is Monitor.py being used extensively?
> 
> It appears that it is incompatible with the AppServer shell 
> script, and
> Launch.py, in that it does not support starting, or 
> restarting the appserver
> with arguments specified to AppServer/Launch...
> 
> Is it intended as an alternate to AppServer/Launch with reduced
> functionality of not supporting command line arguments?
> 
> Seems like you could have Monitor.py replace Launch.py, and 
> have a mode
> where it sticks around to provide continual monitoring, or just does a
> one-shot monitor and exit.  Any time it detects the AppServer is not
> responding, it would do its thing of restarting the 
> appserver.  Perhaps the
> command-line arguments need to be saved in a file and 
> re-loaded to insure
> their re-use?  
> 
> What is AsyncThreadedAppServer?  Is this somethign new, or something
> obsoleted?  Monitor seems to default to this.  It also 
> doesn't look like it
> works with NewThreadedAppServer as-is.

I can't say that I've ever tried to use Monitor.py.  I haven't ever
experienced an appserver crash (even though I'm running on Windows:-) so it
wouldn't have ever helped me.  But we ought to fix it if it's currently
broken in CVS.

AsyncThreadedAppServer is no longer part of Webware -- it has been removed
in CVS.  It was an experimental version of the AppServer that was supposed
to be faster, but turned out to be buggy and slower, so it was removed.

- Geoff