November 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-539?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-539: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support JDK9 build 9-ea+139 > --------------------------- > > Key: MODCLUSTER-539 > URL: https://issues.jboss.org/browse/MODCLUSTER-539 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1, 1.3.6.Final > > > The compiler parameters changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-550) Failover targets should be chosen deterministically

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-550: --------------------------------------- Summary: Failover targets should be chosen deterministically Key: MODCLUSTER-550 URL: https://issues.jboss.org/browse/MODCLUSTER-550 Project: mod_cluster Issue Type: Bug Components: Native (httpd modules) Affects Versions: 1.3.5.Final, 1.2.13.Final Reporter: Paul Ferraro Assignee: Radoslav Husar Fix For: 2.0.0.Alpha1, 1.2.14.Final, 1.3.6.Final Under the following conditions: 1. A request arrives for a session with an unknown route 2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover ... the failover target must be chosen in a deterministic way. This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session. Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-534) Httpd Camel case balancer name not found

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-534?page=com.atlassian.jira.pl... ] Michal Karm Babacek closed MODCLUSTER-534. ------------------------------------------ > Httpd Camel case balancer name not found > ---------------------------------------- > > Key: MODCLUSTER-534 > URL: https://issues.jboss.org/browse/MODCLUSTER-534 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Reporter: Bogdan Sikora > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1, 1.3.4.Final > > > Apache with balancer named with camel case name, sees workers correctly > {noformat} > <html><head> > <title>Mod_cluster Status</title> > </head><body> > <h1>mod_cluster/1.3.1.Final</h1><a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&refresh=10">Auto Refresh</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=DUMP&Range=ALL">show DUMP output</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=INFO&Range=ALL">show INFO output</a> > <h1> Node jboss-eap-7.0 (ajp://10.16.92.87:8009): </h1> > <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=ENABLE-APP&Range=NODE&JVMRoute=jboss-eap-7.0">Enable Contexts</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=DISABLE-APP&Range=NODE&JVMRoute=jboss-eap-7.0">Disable Contexts</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=STOP-APP&Range=NODE&JVMRoute=jboss-eap-7.0">Stop Contexts</a><br/> > Balancer: QA-bAlAnCeR,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 2,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 44 > <h2> Virtual Host 1:</h2><h3>Contexts:</h3><pre>/clusterbench, Status: ENABLED Request: 0 <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=DISABLE-APP&Range=CONTEXT&JVMRoute=jboss-eap-7.0&Alias=default-host&Context=/clusterbench">Disable</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=STOP-APP&Range=CONTEXT&JVMRoute=jboss-eap-7.0&Alias=default-host&Context=/clusterbench">Stop</a> > </pre><h3>Aliases:</h3><pre>default-host > localhost > </pre><h1> Node jboss-eap-7.0-2 (ajp://10.16.92.87:8110): </h1> > <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=ENABLE-APP&Range=NODE&JVMRoute=jboss-eap-7.0-2">Enable Contexts</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=DISABLE-APP&Range=NODE&JVMRoute=jboss-eap-7.0-2">Disable Contexts</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=STOP-APP&Range=NODE&JVMRoute=jboss-eap-7.0-2">Stop Contexts</a><br/> > Balancer: QA-bAlAnCeR,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 2,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 36 > <h2> Virtual Host 1:</h2><h3>Contexts:</h3><pre>/clusterbench, Status: ENABLED Request: 0 <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=DISABLE-APP&Range=CONTEXT&JVMRoute=jboss-eap-7.0-2&Alias=default-host&Context=/clusterbench">Disable</a> <a href="/mcm?nonce=dbf6a14d-f4e6-46fc-88a7-a1851d9fd74e&Cmd=STOP-APP&Range=CONTEXT&JVMRoute=jboss-eap-7.0-2&Alias=default-host&Context=/clusterbench">Stop</a> > </pre><h3>Aliases:</h3><pre>default-host > localhost > </pre></body></html> > {noformat} > but request that should be routed to workers ends with 404 > {noformat} > 07:31:15.536 [INFO] Verifying URL: http://10.16.92.87:2080/clusterbench/jvmroute for response code 200 and content to: contain "" > Aug 23, 2016 7:31:15 AM com.gargoylesoftware.htmlunit.WebClient printContentIfNecessary > INFO: statusCode=[404] contentType=[text/html] > Aug 23, 2016 7:31:15 AM com.gargoylesoftware.htmlunit.WebClient printContentIfNecessary > INFO: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /clusterbench/jvmroute was not found on this server.</p> > <hr> > <address>Apache/2.4.6 (Red Hat) Server at 10.16.92.87 Port 2080</address> > </body></html> > {noformat} > this is part of balancer debug log but from another run > {noformat} > [Tue Aug 23 08:41:47.468099 2016] [authz_core:debug] [pid 17958] mod_authz_core.c(809): [client 127.0.0.1:54932] AH01626: authorization result of Require all granted: granted > [Tue Aug 23 08:41:47.468117 2016] [authz_core:debug] [pid 17958] mod_authz_core.c(809): [client 127.0.0.1:54932] AH01626: authorization result of <RequireAny>: granted > [Tue Aug 23 08:41:47.474707 2016] [:debug] [pid 17959] mod_proxy_cluster.c(2105): get_context_host_balancer: balancer balancer://QA-bAlAnCeR not found > [Tue Aug 23 08:41:47.474727 2016] [:debug] [pid 17959] mod_proxy_cluster.c(2105): get_context_host_balancer: balancer balancer://QA-bAlAnCeR not found > [Tue Aug 23 08:41:47.474767 2016] [authz_core:debug] [pid 17959] mod_authz_core.c(809): [client 127.0.0.1:49024] AH01626: authorization result of Require all granted: granted > [Tue Aug 23 08:41:47.474770 2016] [authz_core:debug] [pid 17959] mod_authz_core.c(809): [client 127.0.0.1:49024] AH01626: authorization result of <RequireAny>: granted > [Tue Aug 23 08:41:47.474809 2016] [core:info] [pid 17959] [client 127.0.0.1:49024] AH00128: File does not exist: /opt/jbcs-httpd24-2.4/httpd/www/html/clusterbench/jvmroute > [Tue Aug 23 08:41:48.979620 2016] [:debug] [pid 17960] mod_proxy_cluster.c(2105): get_context_host_balancer: balancer balancer://QA-bAlAnCeR not found > [Tue Aug 23 08:41:48.979638 2016] [:debug] [pid 17960] mod_proxy_cluster.c(2105): get_context_host_balancer: balancer balancer://QA-bAlAnCeR not found > {noformat} > [Full debug log|https://da.gd/57CQ] > [Test log to debug log|http://pastebin.test.redhat.com/405176] > (on Redhat pastebin because of fedora paste bit was accusing me of spam ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-539?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-539: -------------------------------------- Fix Version/s: 1.3.6.Final > Support JDK9 build 9-ea+139 > --------------------------- > > Key: MODCLUSTER-539 > URL: https://issues.jboss.org/browse/MODCLUSTER-539 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1, 1.3.6.Final > > > The compiler parameters changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-539?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-539: -------------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/220, https://github.com/modcluster/mod_cluster/pull/225 (was: https://github.com/modcluster/mod_cluster/pull/220) > Support JDK9 build 9-ea+139 > --------------------------- > > Key: MODCLUSTER-539 > URL: https://issues.jboss.org/browse/MODCLUSTER-539 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1, 1.3.6.Final > > > The compiler parameters changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-539?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-539: -------------------------------------- Priority: Major (was: Minor) > Support JDK9 build 9-ea+139 > --------------------------- > > Key: MODCLUSTER-539 > URL: https://issues.jboss.org/browse/MODCLUSTER-539 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: jdk9 > Fix For: 2.0.0.Alpha1 > > > The compiler parameters changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-539) Support JDK9 build 9-ea+139

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-539?page=com.atlassian.jira.pl... ] Radoslav Husar reopened MODCLUSTER-539: --------------------------------------- Reopening -- this is needed for 1.3.x as well. > Support JDK9 build 9-ea+139 > --------------------------- > > Key: MODCLUSTER-539 > URL: https://issues.jboss.org/browse/MODCLUSTER-539 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: jdk9 > Fix For: 2.0.0.Alpha1 > > > The compiler parameters changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-505: ---------------------------------------------------- errata-xmlrpc <errata-xmlrpc(a)redhat.com> changed the Status of [bug 1310582|https://bugzilla.redhat.com/show_bug.cgi?id=1310582] from MODIFIED to ON_QA > ProxyErrorOverride=On causes workers in error state after 500 errors > --------------------------------------------------------------------- > > Key: MODCLUSTER-505 > URL: https://issues.jboss.org/browse/MODCLUSTER-505 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.12.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.14.Final, 1.3.5.Final > > > When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-500) Consider dropping base container module; copy container integration code to every integration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-500?page=com.atlassian.jira.pl... ] Radoslav Husar closed MODCLUSTER-500. ------------------------------------- Resolution: Rejected Considered for v2, but turned out to be way too much code duplication (>1K LOC) with standard maven modules setup. Would need to use conditional code inclusions at the build time to be reasonable. > Consider dropping base container module; copy container integration code to every integration > --------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-500 > URL: https://issues.jboss.org/browse/MODCLUSTER-500 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > The main reason for this would be to do the build process right in one take and thus simplify installation (and CI too). > Just comparing Java code: > {noformat} > [rhusar@syrah container]$ find tomcat6 -name '*.java' | xargs wc -l > 678 total > [rhusar@syrah container]$ find tomcat7 -name '*.java' | xargs wc -l > 754 total > [rhusar@syrah container]$ find tomcat8 -name '*.java' | xargs wc -l > 794 total > [rhusar@syrah container]$ find tomcat9 -name '*.java' | xargs wc -l > 1121 total > [rhusar@syrah container]$ find catalina -name '*.java' | xargs wc -l > 3359 total > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-505: ---------------------------------------------------- errata-xmlrpc <errata-xmlrpc(a)redhat.com> changed the Status of [bug 1391517|https://bugzilla.redhat.com/show_bug.cgi?id=1391517] from MODIFIED to ON_QA > ProxyErrorOverride=On causes workers in error state after 500 errors > --------------------------------------------------------------------- > > Key: MODCLUSTER-505 > URL: https://issues.jboss.org/browse/MODCLUSTER-505 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.12.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.14.Final, 1.3.5.Final > > > When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues November 2016