[ 
https://issues.apache.org/jira/browse/OFBIZ-10765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758510#comment-16758510
 ] 

Michael Brohl commented on OFBIZ-10765:
---------------------------------------

Next finding:

 Tomcat.getHost(), which is called in CatalinaContainer.prepareHost(..) does 
return:
{noformat}
 {webapp2=StandardEngine[default-server].StandardHost[webapp2], 
0.0.0.0=StandardEngine[default-server].StandardHost[0.0.0.0], 
 webapp3=StandardEngine[default-server].StandardHost[webapp3], 
webapp1=StandardEngine[default-server].StandardHost[webapp1], 
 ...}{noformat}
webapp2 is the first entry while I think 0.0.0.0 should be.

 

> Failed registration for virtual hosts with similar mount points
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-10765
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10765
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12
>            Reporter: Michael Brohl
>            Assignee: Michael Brohl
>            Priority: Blocker
>             Fix For: 17.12.01, 18.12.01
>
>         Attachments: 
> OFBIZ-10765_failed_registration_for_similar_mount_points.patch
>
>
> The registration of webapps with virtual hosts using similar mount points 
> does not work.
> Example
> The following webapps should be registered (virtual host/ mount point)
>  * host1/webcontent
>  * host2/webcontent
> During registration, the name of the context is implicitly set through the 
> setPath(...) method in org.apache.catalina.core.StandardContext if not 
> already set. In the above example, the name will be set as "/webcontent".
> Wenn the context is added, it is checked if a child under the name is already 
> registered and the addition will be refused.
> The solution would be to explicitly set the name from the webappInfo.name 
> before the path is set. I will provide a patch for it.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to