In case I haven't mentioned it enough, we are running Lenya1.2.2. On 6/25/05, Lee Carroll <[EMAIL PROTECTED]> wrote: > >At the urging of everybody, I am changing my production installation > >from running Lenya under Tomcat to running Lenya using the included > >Jetty. > I'm running lenya within tomcat. What are your reasons for the change? at > who's prompting?
Some of the Lenya developers state Lenya on Jetty is MUCH faster than Lenya on Tomcat. My current project is very dynamic, and it is noticeably slow under Tomcat. I am hoping switching to Jetty is the cure. Otherwise I'll need to play with Tomcat's settings. The other advantage will be to allow multiple instances of Lenya/Jetty. They would each have their own JVM (eating memory, but maybe faster), and their own port. (Apache httpd will proxy the virtual server requests. The Lenya port will be firewalled.) On 6/25/05, Sean Fulton <[EMAIL PROTECTED]> wrote: > On 2005-06-25 15:29:19 -0400, <[EMAIL PROTECTED]> said: > > I could not find any command to shutdown Lenya when running using > > Jetty. There is no "stop" option in lenya.sh. Why not, and what is > > the workaround? > I believe the workaround for stopping Lenya is to simply kill it. You > could have your init script write the lenya PID it a file in /var/run > and add an option to the init script for stopping it. Take look at some > of the other intit.d scripts for examples. Yes, that is the standard for poorly designed programs. It feels like a great way to cause memory leaks. I am hoping Jetty/Lenya is better designed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
