[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-566) Exclusion list cannot be pre-populated eagerly on startup

[Radoslav Husar (JIRA)]

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

Radoslav Husar updated MODCLUSTER-566:
--------------------------------------
         Description: The exclusion list is unnecessarily populated eagerly on init(). This does not work in container such as WildFly where services are started asynchronously and virtual hosts and contexts can be added at any time.  (was: 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.)
    Git Pull Request:   (was: https://github.com/modcluster/mod_cluster/pull/194, https://github.com/modcluster/mod_cluster/pull/195, https://github.com/modcluster/mod_cluster/pull/196)
             Summary: Exclusion list cannot be pre-populated eagerly on startup  (was: Excluded contexts which are not specific to a host should be excluded on all hosts)
         Environment:     (was: Tomcat8 (haven't tried elsewhere yet); mod_cluster version 2.0.0.Alpha1-SNAPSHOT)


> Exclusion list cannot be pre-populated eagerly on startup
> ---------------------------------------------------------
>
>                 Key: MODCLUSTER-566
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-566
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.3.6.CR1
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>
> The exclusion list is unnecessarily populated eagerly on init(). This does not work in container such as WildFly where services are started asynchronously and virtual hosts and contexts can be added at any time.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)