[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-509) Excluded contexts which are not specific to a host should be excluded on all hosts

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
    Summary: Excluded contexts which are not specific to a host should be excluded on all hosts  (was: Excluded contexts not specific to a host should be excluded on all hosts)


> Excluded contexts which are not specific to a host should be excluded on all hosts
> ----------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-509
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-509
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.3.2.Final, 1.2.12.Final, 2.0.0.Alpha1
>         Environment: Tomcat8 (haven't tried elsewhere yet); mod_cluster version 2.0.0.Alpha1-SNAPSHOT
>            Reporter: Michal Karm Babacek
>            Assignee: Radoslav Husar
>            Priority: Critical
>             Fix For: 1.3.3.Final, 2.0.0.Alpha1, 1.2.13.Final
>
>
> With the following configuration:
> {code}
> <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener" 
> loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" 
> loadMetricCapacity="1" 
> loadHistory="9" 
> loadDecayFactor="2" 
> stickySession="true" 
> stickySessionForce="false" 
> stickySessionRemove="true" 
> advertise="true" 
> advertiseGroupAddress="224.0.1.105"
> advertisePort="23364"
> advertiseInterface="10.40.4.50"
> excludedContexts="ROOT,docs,manager,host-manager,examples"
> />
> {code}
> And these contexts in webapps:
> {code}
> clusterbench docs  examples  host-manager  manager  ROOT
> {code}
> One expects this output on Mod_cluster manger console:
> {code}
> Virtual Host 1:
> Contexts:
> /clusterbench, Status: ENABLED Request: 0 Disable Stop
> Aliases:
> localhost
> {code}
> It works, unless you configure additional VirtualHosts:
> {code}
> <Host name="LOCALHOST"  appBase="webapps" unpackWARs="true" autoDeploy="true">
> <Alias>LOCALHOST</Alias>
> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
>        prefix="localhost_access_log" suffix=".txt"
>        pattern="%h %l %u %t &quot;%r&quot; %s %b" />
> </Host>
> <Host name="KARM.BRQ.REDHAT.COM" appBase="webapps" unpackWARs="true" autoDeploy="true">
> <Alias>KARM.BRQ.REDHAT.COM</Alias>
> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
>        prefix="localhost_access_log" suffix=".txt"
>        pattern="%h %l %u %t &quot;%r&quot; %s %b" />
> </Host>
> {code}
> result:
> {code}
> Node worker1 (ajp://10.40.4.50:8009):
> Enable Contexts Disable Contexts Stop Contexts
> Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 100
> Virtual Host 2:
> Contexts:
> /docs, Status: ENABLED Request: 0 Disable Stop
> /manager, Status: ENABLED Request: 0 Disable Stop
> /host-manager, Status: ENABLED Request: 0 Disable Stop
> /examples, Status: ENABLED Request: 0 Disable Stop
> /, Status: ENABLED Request: 0 Disable Stop
> /clusterbench, Status: ENABLED Request: 0 Disable Stop
> Aliases:
> karm.brq.redhat.com
> Virtual Host 1:
> Contexts:
> /clusterbench, Status: ENABLED Request: 0 Disable Stop
> Aliases:
> localhost
> {code}
> I find this bug being of Critical priority, because it could coax users into believing they excluded certain context while in fact they didn't.
> WDYT? Is it possible to tweak with the Listener's configuration somehow?
> THX.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)