[MAGNOLIA-1643] Magnolia does not deploy when using multiple virtual hosts Created: 25/Jul/07 Updated: 23/Jan/13 Resolved: 10/Aug/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | zam6ak | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
3.1-SNAPSHOT |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
In order to perform load balancing while allowing multiple subscribers, we have to deploy 2 Magnolia public instances. For example node1 - vhosts: node2 - vhosts 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. -----SETUP TO REPRODUCE EXCEPTION (JBoss 4.0.5) ---- i" "% {User-Agent}i" "% {Cookie}i"" 2. Add jboss-web to WEB-INF/ folder of the webapp. 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). |
| Comments |
| Comment by Magnolia International [ 27/Jul/07 ] |
|
| Comment by zam6ak [ 27/Jul/07 ] |
|
Attaching magnolia-debug.log |
| Comment by zam6ak [ 27/Jul/07 ] |
|
Removed long and uninformative stacktrace from the issue Description |
| Comment by Philipp Bracher [ 10/Aug/07 ] |
|
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. |