[JBoss JIRA] (MODCLUSTER-515) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
Radoslav Husar created MODCLUSTER-515:
-----------------------------------------
Summary: excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
Key: MODCLUSTER-515
URL: https://issues.jboss.org/browse/MODCLUSTER-515
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 "%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>
{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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Merged to all 3 branches.
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
Status: Pull Request Sent (was: Pull Request Sent)
Git Pull Request: https://github.com/modcluster/mod_cluster/pull/194, https://github.com/modcluster/mod_cluster/pull/195, https://github.com/modcluster/mod_cluster/pull/196 (was: https://github.com/modcluster/mod_cluster/pull/194)
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
Fix Version/s: 1.2.13.Final
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/modcluster/mod_cluster/pull/194
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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
>
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
Workaround Description:
You need to specify every exclusion *per host*, e.g.:
{{excludedContexts="localhost:ROOT,localhost:docs,localhost:manager,localhost:host-manager,localhost:examples,localhost2:ROOT,localhost2:docs,localhost2:manager,localhost2:host-manager,localhost2:examples"}}
Workaround: Workaround Exists
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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
>
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Work on MODCLUSTER-509 started by Radoslav Husar.
-------------------------------------------------
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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
>
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-509) excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-509?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-509:
--------------------------------------
Summary: excludedContexts attribute doesn't work for all Tomcat's VirtualHosts (was: excludedContexts attribut doesn't work for all Tomcat's VirtualHosts)
> excludedContexts attribute doesn't work for all Tomcat's VirtualHosts
> ---------------------------------------------------------------------
>
> 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
>
>
> 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 "%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>
> {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)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-514) MemManagerFile doesn't take relative paths
by Michal Karm Babacek (JIRA)
Michal Karm Babacek created MODCLUSTER-514:
----------------------------------------------
Summary: MemManagerFile doesn't take relative paths
Key: MODCLUSTER-514
URL: https://issues.jboss.org/browse/MODCLUSTER-514
Project: mod_cluster
Issue Type: Bug
Components: Native (httpd modules)
Affects Versions: 1.3.1.Final, 1.2.13.Final
Reporter: Michal Karm Babacek
Assignee: Michal Karm Babacek
Priority: Minor
This is mostly a user experience issue.
According to what {{LoadModule}} and other directives do, one would expect that a path without leading slash is a relative one to the server root.
h3. Setting
* {{MemManagerFile cache/mod_cluster}}
* {{ServerRoot "/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build"}}
h3. Expected result
{noformat}
/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/cache/mod_cluster/
manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes
manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock
manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem
{noformat}
h3. Actual result
{noformat}
/cache/mod_cluster/
manager.balancer.balancers manager.context.contexts manager.domain.domain manager.host.hosts manager.node.nodes
manager.balancer.balancers.lock manager.context.contexts.lock manager.domain.domain.lock manager.host.hosts.lock manager.node.nodes.lock
manager.balancer.balancers.slotmem manager.context.contexts.slotmem manager.domain.domain.slotmem manager.host.hosts.slotmem manager.node.nodes.slotmem
{noformat}
and an empty directory is created in the directory from which the httpd root process was started:
{{/home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/bin/cache/mod_cluster/}}.
h3. Fix
* leading {{/}} should mean absolute path
* without leading {{/}} should be relative to ServerRoot
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (MODCLUSTER-513) Discovery in cloud environments
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-513?page=com.atlassian.jira.pl... ]
Michal Karm Babacek commented on MODCLUSTER-513:
------------------------------------------------
How about we take that simple Azure's java lib currently used for JGroups-extras "Azure PING" and create a new Wildfly subsystem, "Cloud Storage" that could offer other subsystems the functionality via a common WF API? JGroups could use it, mod_cluster, WF Discovery...
h3. Meet JClouds
JClouds incorporates many provides, AWS, GCE, Azure, OpenStack... and abstracts their APIs. Obviously, we are not interested in spinning up new VMs, but we could leverage it's functionality for an ubiquitous access to "blob storage". At least GCE, Azure and AWS offer this service; JClouds abstracts their APIs. [~jcacek] is a Distinguished Senior Principal JClouds consultant, so he could drop a comment here :)
h3. Do it ourselves
If JClouds proves to be too heavy for such a simple task, we could add providers one by one:
{code}
<subsystem xmlns="urn:jboss:domain:cloudblob:1.0">
<provider name="azure">
<credentials apikey="yadayada" subscriptionid="blablabla"/>
<storage-config>....</storage-config>
<provider/>
<provider name="ec2">
<credentials apikey="yadayada"/>
<storage-config>....</storage-config>
<provider/>
<provider name="gce">
<credentials user="yadayada" certificate-path="/bla/bla/..."/>
<storage-config>....</storage-config>
<provider/>
</subsystem>
{code}
> Discovery in cloud environments
> -------------------------------
>
> Key: MODCLUSTER-513
> URL: https://issues.jboss.org/browse/MODCLUSTER-513
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java), Native (httpd modules)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 2.0.0.Alpha1
>
>
> Currently we only support multicast-based discovery and static configuration none of which is suitable for the clouds.
> Ideally we should generalize discovery and support pluggable implementations (could wildfly-discovery be a starting point?).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months