[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-186) Proxy Discovery Configuration property excludedContexts is not set to default when running under Tomcat
Jean-Frederic Clere (Jira)
issues at jboss.org
Wed May 8 08:37:00 EDT 2019
[ https://issues.jboss.org/browse/MODCLUSTER-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Frederic Clere resolved MODCLUSTER-186.
--------------------------------------------
Resolution: Out of Date
> Proxy Discovery Configuration property excludedContexts is not set to default when running under Tomcat
> -------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-186
> URL: https://issues.jboss.org/browse/MODCLUSTER-186
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.1.0.Final
> Environment: Tomcat 6.0.29
> Reporter: Ruslan Gainutdinov
> Assignee: Jean-Frederic Clere
> Priority: Major
> Labels: mod_cluster, tomcat
>
> The documentation
> http://docs.jboss.org/mod_cluster/1.1.0/html/java.properties.html
> states that excludedContexts have default value of
> ROOT, admin-console, invoker, bossws, jmx-console, juddi, web-console
> However, under Tomcat, it is not the case.
> When org.jboss.modcluster.ModClusterService.init() is called mcmpConfig.excludedContexts is null.
> One have to manually specify
> <Listener className="org.jboss.modcluster.catalina.ModClusterListener"
> excludedContexts="ROOT,manager,host-manager"/>
> Best fix will be to set it excludedContexts="ROOT,manager,host-manager"
> as default under Tomcat.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the mod_cluster-issues
mailing list