From: Chris H. <ch...@ha...> - 2003-09-29 16:59:10
|
Tricky. The problem is that once Java classes get loaded into the Java Virtual Machine you have to stop it (unless it's one of the special JVMs which supports class re-loading). The three major options I can think of for your situation are: 1) See if anyone has a solution to offer using a JVM which re-loads classes. It's not standard Jetty, but some people have discussed this here in the past. Suggestions / experience anyone??? 2) Use a separate Jetty-in-a-JVM for each webapp and a common 'front-end' Jetty configured as a proxy. Then you can start and stop the separate JVMs at will. 3) Use a single Jetty instance which has to be restarted when any of its webapps is to be deleted or updated. This does not meet the requirement. but if no SSH is in use this takes only a few seconds. The new start.jar and stop.jar make this easy and quick to implement. HTH Chris Daryl replied: > Hi Chris, > > I set up a new machine for them and installed 4.2.12 and then just moved > their webapps over and looked at how they were starting Jetty on the > old box. I and they are absolutely open to learning new things :-) > > Yes each site may need to have different classes that need to be updated > and a couple more sites will be added. Having each site "live" > independently just makes sense. > > Thank you for taking the time to respond! > Daryl > > > > Chris Haynes wrote: > > HI Daryl, welcome to the list. > > > > The final answers may have to come from Greg, but I can attempt some > > 'triage' to save time. > > > > May I first ask for some additional info: > > > > 1) As your clients are using jetty.sh it appears they are using an > > older version. More recent versions have a better (and perhaps more > > relevant) start-stop mechanism. Would there be any objection to > > upgrading Jetty if necessary? > > > > 2) Why do they want to 'start and stop' the services? Is it to shut > > off external availability, because the different virtual sites have > > different sets of Servlets / JSPs whose classes need to be updated > > and reloaded into the JVM, or what? A clear idea of their actual > > _requirements_ is needed, because, as stated so far, the proposed > > 'solution' of starting and stopping individual services does not > > really make much sense. > > > > > > Chris > > > > > > > > > >>I have been asked by my client, for which I administer their Linux > > > > box, > > > >>to configure Jetty such that each of the web sites that come to this > > > > box > > > >>can be started and stopped independently. They were using Jetty > > > > before > > > >>I entered the picture. I read in the Jetty tutorial documentation > > > > that > > > >>each site can have its own server: > >> > >> SocketListener --> HttpServer --> HttpContext --> HttpHandler(s) > >> host:www.alpha.com path:"/" > >> port:80 > >> > >> SocketListener --> HttpServer --> HttpContext --> HttpHandler(s) > >> host:www.beta.com path: "/" > >> port:80 > >> > >> Diagram: Multiple servers > >> > >>however, being new to Jetty I am not seeing how to modify their > > > > current > > > >>etc/jett.xml to achieve this. Can anyone enlighten me on this? > > > > Also, I > > > >>suspect bin/jetty.sh will need some modification to support this, > > > > correct? > > > >>Thank you kindly, > >>Daryl |