-
Bug
-
Resolution: Not an issue
-
Major
-
None
-
4.4.2
-
None
-
Apache Tomcat 6.0.18, Java 6 (1.6.0_17), Magnolia 4.4.2, Linux RHEL 2.6
-
-
Empty show more show less
I'm having an issue deploying a Magnolia application to Tomcat 6 using the ROOT.xml/ROOT webapp method.
The magnolia web application has multiple instances within it (my_site, my_site_test, author) and up until now we've had the Context configuration entered directly into the Host section of our server.xml. Our current solution works but we have a new need for automating deployments via the Tomcat manager and the use of server.xml for Contexts precludes this.
According to the Tomcat 6 documentation (http://tomcat.apache.org/tomcat-6.0-doc/config/context.html), I should be able to add a file located at $CATALINA_BASE/conf/[enginename]/[hostname]/ROOT.xml, which in our configuration is $CATALINA_BASE/conf/my_site/x.x.x.x/ROOT.xml. Because this causes the context path to be renamed "ROOT" or "", Magnolia can't infer the correct instance from the context name itself (I believe). So I've added the following to the Context in ROOT.xml:
<Parameter name="instance" value="my_site" override="false" />
Which should cause Magnolia to choose the my_site instance. However, it doesn't appear to do so and instead I'm getting a default instance (author). Author is running on a separate tomcat instance, which is why the repository appears locked in the error log.
Thanks, please let me know if you need any more information.