Kendall Clark wrote: > >>>>> "tavis" == Tavis Rudd <[EMAIL PROTECTED]> writes: > > tavis> Actually, I have other hopes for the monitor process as well: > tavis> - scheduled restarts > tavis> - triggered restarts on any number of user specified > tavis> conditions > tavis> - memory and cpu usage profiling/throttling > tavis> - response time profiling > > tavis> I gotta admit that my interest comes from the cool factor, > tavis> rather than an actual need on my part, but it would be fun to > tavis> code. > > I don't need *all* of that, but since I'm gonna be using Webware to > host web apps, for paying customers, on several boxes, across many > virtual domains, some of it would be nice. > > It's that *kind* of stuff that would help make Webware seem more > attractive to the "enterprise" crowd, including ISPs. Having such a > monitoring solution would make selling Webware, as a consultant, > against the Java App Server easier, too. Nothing wrong with that. > > And if I were a colo-host or big ISP, that kind of solution would > certainly make me more likely to consider allowing or providing > Webware for my customers. > > Good ideas, Tavis.
If you work on this, try to modularize the OS-specific parts as much as possible. Windows and Unix will require very different ways of monitoring memory and cpu. And the method for restarting the appserver will be quite different too. But much of the logic should be identical. Perhaps a small class can be written that handles the os-specific parts, and a different class can be swapped in for the Windows version. - Geoff _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
