-
Bug
-
Resolution: Done
-
Critical
-
10.0.0.Final
-
None
-
None
With the following configuration:
<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" />
And these contexts in webapps:
clusterbench docs examples host-manager manager ROOT
One expects this output on Mod_cluster manger console:
Virtual Host 1: Contexts: /clusterbench, Status: ENABLED Request: 0 Disable Stop Aliases: localhost
It works, unless you configure additional VirtualHosts:
<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 "%r" %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 "%r" %s %b" /> </Host>
result:
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
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.
- clones
-
JBEAP-5058 Excluded contexts which are not specific to a host should be excluded on all hosts
- Verified
- is blocked by
-
MODCLUSTER-566 Exclusion list cannot be pre-populated in init()
- Resolved