Michael Dehmlow wrote: > Thanks, my version of tomcat 5.5.26. My mistake I was looking at tomcat 3.3 > documentation: > http://tomcat.apache.org/tomcat-3.3-doc/tomcat-apache-howto.html > http://tomcat.apache.org/tomcat-3.3-doc/tomcat-apache-howto.html . > > Yes defining contexts in the Server.xml is discouraged but I'm doing it > anyway. ;)
Strongly suggested. > For those in a similar situation I'm going down the path of defining an > engine per context: Still won't give you separate JVMs. As Peter and Chuck indicated, you'll need to create separate Tomcat instances if you want to have separate JVMs. When you start Tomcat you are calling Java's JVM first, then Tomcat runs inside of it. If you want another JVM instance you have to start another completely external process. The JVMs don't run inside Tomcat, it's the other way round. > <Engine name="engA" defaultHost="localhost" jvmRoute="jvmA"> > <Host name="localhost" appBase="webapps" > unpackWARs="true" > xmlValidation="false" xmlNamespaceAware="false"> > <Context path="/eclipse/A" docBase="/slot_A" > cookies='false'> > <Parameter name="com.dev.myParm" value="/eclipse/A" > override="true"/> > </Context> > </Host> > </Engine> > > Using jvmRoute the idea is to use the clustering mechanism of tomcat to give > me multiple jvms.... I think you're mistaking jvmRoute for something it isn't. This attribute is used to add a marker to the jsessionid so that routing devices in front of a cluster of Tomcat servers can determine which server to send a sticky session to. http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html > This being only my theory I can only hope someone can either call me an > idiot or give me a few pointers in short order. http://tomcat.apache.org/tomcat-5.5-doc/ p > I will post my findings as I find them. > Thanks, > Mike --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
