Chris Thanks for taking the time to explain this to me. I'm still trying to absorb it all. More below.
> > My question is this. Is it even possible or simply not recommended > > for both tomcat instances to share the same CATALINA_BASE? The work > > folder with compiled cache is buried in CATALINA_HOME, not under > > webapps, right? It also assumes that no changes need to be made to > > the application code or web.xml to accommodate the newer tomcat > > version. If changes need to be made for the new version, then the > > whole issue becomes moot. > So I would recommend a separate CATALINA_BASE for each application's > support for a major Tomcat version. Note that you are welcome to share > WAR files for an application. > > Example: > > Tomcat 6 CATALINA_BASE: > bin/setenv.sh > conf/server.xml > conf/context.xml > conf/web.xml > conf/Catalina/localhost/mywebapp.xml [ references C:\apps\myapp.war ] > > Tomcat 8.5 CATALINA_BASE > bin/setenv.sh > conf/server.xml > conf/context.xml > conf/web.xml > conf/Catalina/localhost/mywebapp.xml [ references C:\apps\myapp.war ] > > In this way, your CATALINA_BASE directory only contains a handful of > configuration files (plus the work/ directory, but you let Tomcat > worry about that). We host multiple apps. So each app instance would require its own CATALINA_BASE for each instance of Tomcat? This is beginning to sound like a matrix nightmare. :-) > If you update your WAR file, both services will be updated with your > latest code. We don't (yet) use WAR files, but rather exploded directories. In your example, can conf/Catalina/localhost/mywebapp.xml reference C:\apps\myapp (folder)? -- Cris Berneburg CACI Lead Software Engineer
