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. ;)
For those in a similar situation I'm going down the path of defining an
engine per context:
<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....
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.
I will post my findings as I find them.
Thanks,
Mike
--
View this message in context:
http://www.nabble.com/JVM-per-Context-tp19414891p19420413.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
