Costin Manolache wrote: > Pier Fumagalli wrote: > > >>"Costin Manolache" <[EMAIL PROTECTED]> wrote: >> >> >>>- starting a VM using exec / monitor the child process. It is not >>>implemented yet in jk2 - but pretty important ( it's one of the features >>>from jserv that wasn't yet ported). It seems daemon has a bit >>>of code - as I mentioned from reading it I don't think it works, >>>and it would be better to use the code from jserv for this - whenever >>>we do implement this. >> >>That was the feature which created more problems in JServ... I remember me >>and Ed hammering on it for months in 97/98. My hint, forget about it, also >>because if you tie it to the web server process, when you take down the >>Web Server, also your servlet engine is going to go down, and that's not a >>very desirable feature given how much time it takes to initialize 7/8 web >>applications.... > > > I know about this - and I wasn't thinking to implement it in the same way > ( i.e. have the web server directly start/stop tomcat ). > > The 'feature' is that all tomcat processes ( and you may run more than > one in a load balanced mode ) can be started automatically and monitored. > If one dies, it'll be automatically restarted.
What do you plan to use to do the real-time monitoring ? Threads embedded in Apache 2.0 or will Apache 2.0 execing daemon/service monitors which in turn launch and monitor the JVM ? > To make things interesting, this information ( and other like that ) needs > to be communicated to apache servers ( to stop sending requests to > not-ready servers ), and potentially to an eventual JMX proxy. This is > the kind of 'control channel' that was proposed several times and will > have to be implemented for other purposes. Ajp13++ ? Well with that proposal, we'll be very similar to WebSphere for example, which have such features, and allow a sysadmin to launch instance (JVM) from a single control panel. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
