[ http://jira.magnolia.info/browse/MAGNOLIA-1643?page=all ]
Philipp Bracher resolved MAGNOLIA-1643.
---------------------------------------
Resolution: Won't Fix
Assignee: Philipp Bracher (was: Boris Kraft)
The described configuration triggers twice a start of the context. Since the
context listener starts the application this initializes jackrabbit twice as
well. This is dangerous! Don't do that! Use an alias instead (server.xml).
Remark: to define a subscriber you can use the ip and context if you have to.
We normally don't configure this on the jboss or tomcat we use an apache in
front to handle virtual hosts resolution.
> Magnolia does not deploy when using multiple virtual hosts
> ----------------------------------------------------------
>
> Key: MAGNOLIA-1643
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1643
> Project: Magnolia
> Issue Type: Bug
> Environment: 3.1-SNAPSHOT
> JBoss 4.0.5 / Tomcat 5.5
> Reporter: Amir Mistric
> Assigned To: Philipp Bracher
> Attachments: magnolia-debug.log
>
>
> In order to perform load balancing while allowing multiple subscribers, we
> have to deploy 2 Magnolia public instances.
> Each instance has to be is bound to 2 virtual host names - one for
> loadbalancing purposes and one for subscription purposes
> For example
> node1 - vhosts:
> +site.company.org
> +site01.company.org
> node2 - vhosts
> +site.company.org
> +site02.company.org
> With this setup a load balancing hardware (like Cisco Content Switch) can use
> site.company,org to perform load balancing while each individual instance can
> still be accessed using either site01 or site02 vhost.
> Vhosting is used to allow multiple apps on the same server to have root
> context (deployed under /)
> -----SETUP TO REPRODUCE EXCEPTION (JBoss 4.0.5) ----
> 1. add new Host entry to
> <jboss_root>/server/all/deploy/jbossweb-tomcat55.sar/server.xml.
> Hhere is an example
> <Host name="fn0161.company.org" autoDeploy="false"
> deployOnStartup="true" deployXML="false">
> <Alias>fn0161</Alias>
> <Valve className="org.apache.catalina.valves.AccessLogValve"
> prefix="fn0161.company.org-"
> suffix="-access_log"
> pattern="%h %v %u %t "%r" %s %b
> "%{Referer}i" "%{User-Agent}i" "%{Cookie}i""
> directory="${jboss.server.log.dir}/access"
> rotatable="true"
> fileDateFormat="yyyy-MM-dd"
> resolveHosts="false" />
> </Host>
> 2. Add jboss-web to WEB-INF/ folder of the webapp.
> Here is an exmple
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN"
> "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd";>
> <jboss-web>
> <context-root>/</context-root>
> <virtual-host>fn0161.company.org</virtual-host>
> <virtual-host>localhost</virtual-host>
> </jboss-web>
> The above setup will allow Magnolia to be deployed under root context "/" and
> only under 2 virtual hosts - "localhost" and "fn0161"
> After restart the exception is thrown (see attached log file).
> If one of the vhosts is removed, everything is fine....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
