March 2020 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-475) Automate built artifacts release to GitHub Releases

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-475?page=com.atlassian.jira.p... ] Jean-Frederic Clere closed MODCLUSTER-475. ------------------------------------------ Resolution: Out of Date > Automate built artifacts release to GitHub Releases > --------------------------------------------------- > > Key: MODCLUSTER-475 > URL: https://issues.redhat.com/browse/MODCLUSTER-475 > Project: mod_cluster > Issue Type: Task > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Major > > The current setup of the suite of our multi-platform Jenkins jobs builds all the release artifacts without pushing them anywhere. > The person doing the release has to download all these built artifacts and upload them to the jboss.org. Next, one has to adjust Magnolia Release pages, Release notes and links. It is tedious, it involves extensive Magnolia and Docbook hacking and we should get rid of it in order to streamline the release process. > MODCLUSTER-474 introduced GitHub Releases, e.g. [1.3.1.Final on GitHub|http://modcluster.io/change_log/#final-6-may-2015]. This particular "demo" was uploaded manually, although it could be nicely automated either with [ghr|https://github.com/tcnksm/ghr] or [github-release|https://github.com/aktau/github-release]. The only possible downside is the exposure of our GitHub keys to the build environment. It could be easily addressed by having the mod_cluster-release Jenkins job tied to a one and only one specific private slave. Other suggestions are welcome though. > Also, let's avoid https://xkcd.com/1319/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-465) CMake: build expat, apr, apru, zlib, iconv, openssl, httpd, jk and mod_cluster

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-465?page=com.atlassian.jira.p... ] Jean-Frederic Clere closed MODCLUSTER-465. ------------------------------------------ Resolution: Won't Fix we will vcpkg instead. > CMake: build expat, apr, apru, zlib, iconv, openssl, httpd, jk and mod_cluster > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-465 > URL: https://issues.redhat.com/browse/MODCLUSTER-465 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Major > Original Estimate: 24 weeks > Remaining Estimate: 24 weeks > > This is a long-term pet project dedicated to translating Autotools to CMake. The first two target platforms are Windows and Fedora, x86_64. Various flavours of Solaris, HP-UX, FreeBSD and Mac will follow. > I'll use this JIRA for tracking notes and progress. It is noteworthy that the current upstream expat, apr and httpd use CMake to generate MSVC projects, so translating those to generating Linux make files shouldn't be that nightmareish. One Autotools directive at a time... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-425) The timeout specified has expired: proxy: AJP: cping/cpong failed, ajp_ilink_receive() can't receive header

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-425?page=com.atlassian.jira.p... ] Jean-Frederic Clere closed MODCLUSTER-425. ------------------------------------------ Resolution: Out of Date > The timeout specified has expired: proxy: AJP: cping/cpong failed,ajp_ilink_receive() can't receive header > ---------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-425 > URL: https://issues.redhat.com/browse/MODCLUSTER-425 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.6.Final, 1.2.9.Final > Environment: Confirmed RHEL6 x86_64 > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Major > > mod_cluster balancer used in front of GateIn Portal, after certain warm-up time, starts to show: > {code} > [debug] proxy_util.c(2200): proxy: connected / to perf13:8009 > [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend > [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done > [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf13) > [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf12) > [debug] proxy_util.c(2074): proxy: connecting ajp://perf12:8009/ to perf12:8009 > [debug] proxy_util.c(2200): proxy: connected / to perf12:8009 > [debug] proxy_util.c(2451): proxy: ajp: fam 2 socket created to connect to perf12 > [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend > [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done > [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf12) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > [error] ajp_handle_cping_cpong: ajp_ilink_receive failed > [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12) > [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf12) > [debug] proxy_util.c(2074): proxy: connecting ajp://perf12:8009/ to perf12:8009 > [debug] proxy_util.c(2200): proxy: connected / to perf12:8009 > [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend > [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done > [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf12) > [debug] proxy_util.c(2018): proxy: ajp: has acquired connection for (perf13) > [debug] proxy_util.c(2074): proxy: connecting ajp://perf13:8009/ to perf13:8009 > [debug] proxy_util.c(2200): proxy: connected / to perf13:8009 > [debug] mod_proxy_cluster.c(1384): proxy_cluster_try_pingpong: connected to backend > [debug] mod_proxy_cluster.c(1108): ajp_cping_cpong: Done > [debug] proxy_util.c(2036): proxy: ajp: has released connection for (perf13) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > [error] ajp_handle_cping_cpong: ajp_ilink_receive failed > [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > [error] ajp_handle_cping_cpong: ajp_ilink_receive failed > [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > [error] ajp_handle_cping_cpong: ajp_ilink_receive failed > [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > [error] ajp_handle_cping_cpong: ajp_ilink_receive failed > [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > [error] ajp_handle_cping_cpong: ajp_ilink_receive failed > [error] (70007)The timeout specified has expired: proxy: AJP: cping/cpong failed to 10.16.88.190:8009 (perf12) > [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header > {code} > Investigation is going on... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-364) mod_cluster and mod_proxy : keeping session

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-364?page=com.atlassian.jira.p... ] Jean-Frederic Clere closed MODCLUSTER-364. ------------------------------------------ Resolution: Cannot Reproduce I can't reproduce the issue. > mod_cluster and mod_proxy : keeping session > ------------------------------------------- > > Key: MODCLUSTER-364 > URL: https://issues.redhat.com/browse/MODCLUSTER-364 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Major > > Why this config: > {noformat} > ProxyPassMatch ^/app/static/ ! > ProxyPass /app balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on > ProxyPass / ! > ProxyPassReverse /app balancer://qacluster > ProxyPassReverseCookieDomain / /app/ > ProxyPassReverseCookiePath / /app/ > ProxyPreserveHost on > {noformat} > does not keep the same session? I keep getting new sessions while hitting F5 with {{http://server:6666/app/clusterbench/requestinfo/}} > *TODO:* Investigate whether it is a configuration error or mod_clutser's incompatibility. > According to this [blog post|http://www.brandonchecketts.com/archives/use-proxypassreversecookied...], it should be trivial :-( -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-702) ProxyPass redirects all requests to modcluster proxy

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-702?page=com.atlassian.jira.p... ] Jean-Frederic Clere closed MODCLUSTER-702. ------------------------------------------ Resolution: Rejected configuration error. > ProxyPass redirects all requests to modcluster proxy > ---------------------------------------------------- > > Key: MODCLUSTER-702 > URL: https://issues.redhat.com/browse/MODCLUSTER-702 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.12.Final > Environment: Centos Linux 7.7.1908 > Apache Web Server 2.4.39 > Reporter: Matt Rummel > Assignee: Jean-Frederic Clere > Priority: Major > Attachments: ModClusterProxyError.conf > > > In Apache Web Server, when mod cluster is enable on a per virtual host basis, CreateBalancers 1, all proxypass directives within a virtual host pass the session to mod cluster even if target is another location such as: > ProxyPass ! > ProxyPass http://notTheBalancer:8213 > See attached document for configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-702) ProxyPass redirects all requests to modcluster proxy

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-702?page=com.atlassian.jira.p... ] Jean-Frederic Clere commented on MODCLUSTER-702: ------------------------------------------------ ProxyPass "/examples" "balancer://mycluster/" ProxyPassReverse "/examples" "balancer://mycluster/" <Location "/docs"> ProxyPass "!" </Location> is NOT the way to exclude context with mod_cluster You need something like: excludedContexts="ROOT,docs" In the <Listener/> in server.xml. > ProxyPass redirects all requests to modcluster proxy > ---------------------------------------------------- > > Key: MODCLUSTER-702 > URL: https://issues.redhat.com/browse/MODCLUSTER-702 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.12.Final > Environment: Centos Linux 7.7.1908 > Apache Web Server 2.4.39 > Reporter: Matt Rummel > Assignee: Jean-Frederic Clere > Priority: Major > Attachments: ModClusterProxyError.conf > > > In Apache Web Server, when mod cluster is enable on a per virtual host basis, CreateBalancers 1, all proxypass directives within a virtual host pass the session to mod cluster even if target is another location such as: > ProxyPass ! > ProxyPass http://notTheBalancer:8213 > See attached document for configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-712) drop support of httpd-2.2.x in branch 1.3.x

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-712?page=com.atlassian.jira.p... ] Radoslav Husar resolved MODCLUSTER-712. --------------------------------------- Resolution: Done > drop support of httpd-2.2.x in branch 1.3.x > ------------------------------------------- > > Key: MODCLUSTER-712 > URL: https://issues.redhat.com/browse/MODCLUSTER-712 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.12.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 1.3.13.Final > > > Per httpd.apache.org 2.2.x is out of support since 2017... Time to clean -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-712) drop support of httpd-2.2.x in branch 1.3.x

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-712?page=com.atlassian.jira.p... ] Radoslav Husar updated MODCLUSTER-712: -------------------------------------- Issue Type: Task (was: Bug) > drop support of httpd-2.2.x in branch 1.3.x > ------------------------------------------- > > Key: MODCLUSTER-712 > URL: https://issues.redhat.com/browse/MODCLUSTER-712 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.12.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 1.3.13.Final > > > Per httpd.apache.org 2.2.x is out of support since 2017... Time to clean -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-712) drop support of httpd-2.2.x in branch 1.3.x

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-712?page=com.atlassian.jira.p... ] Radoslav Husar reopened MODCLUSTER-712: --------------------------------------- [~jfclere] The linked commit is from master branch - 2.x and not from 1.3.x branch. Can you link the right one? Also reopening to fix issue type. > drop support of httpd-2.2.x in branch 1.3.x > ------------------------------------------- > > Key: MODCLUSTER-712 > URL: https://issues.redhat.com/browse/MODCLUSTER-712 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.12.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 1.3.13.Final > > > Per httpd.apache.org 2.2.x is out of support since 2017... Time to clean -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-613) mod_cluster_slotmem doesn't use the same ftok() than apr

by Jean-Frederic Clere (Jira)

[ https://issues.redhat.com/browse/MODCLUSTER-613?page=com.atlassian.jira.p... ] Jean-Frederic Clere closed MODCLUSTER-613. ------------------------------------------ Resolution: Out of Date the corresponding customer case has been closed for years. > mod_cluster_slotmem doesn't use the same ftok() than apr > -------------------------------------------------------- > > Key: MODCLUSTER-613 > URL: https://issues.redhat.com/browse/MODCLUSTER-613 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.0.Final, 1.3.0.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues March 2020