January 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Michal Karm Babacek commented on MODCLUSTER-397: ------------------------------------------------ I will eventually address that. I don't know yet. > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-397: ------------------------------------------- Does the merged PR resolve the issue completely? In that case we should resolve this. > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-397 at 1/13/16 8:46 AM: -------------------------------------------------------------------- Does the merged PR resolve the issue completely? In that case we should resolve this Jira. was (Author: rhusar): Does the merged PR resolve the issue completely? In that case we should resolve this. > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-397: -------------------------------------- Component/s: Native (httpd modules) > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-397: ------------------------------------------------ merged in master. > StickySessions don't work for ProxyPass from unenabled context > -------------------------------------------------------------- > > Key: MODCLUSTER-397 > URL: https://issues.jboss.org/browse/MODCLUSTER-397 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.3.2.Alpha1 > > > Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd: > CreateBalancers 1 > ... > ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-475?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-475: ------------------------------------------- Description: 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/ was: 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. > Automate built artifacts release to GitHub Releases > --------------------------------------------------- > > Key: MODCLUSTER-475 > URL: https://issues.jboss.org/browse/MODCLUSTER-475 > Project: mod_cluster > Issue Type: Task > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > 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 (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-353) SocketTimeoutException in DefaultMCMPHandler when using httpd 2.4.x

by Micheal Delson Nadar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-353?page=com.atlassian.jira.pl... ] Micheal Delson Nadar edited comment on MODCLUSTER-353 at 1/8/16 12:22 AM: -------------------------------------------------------------------------- Update : Its the same with Jboss 7.1.1 and Apache httpd 2.4.12 with mod_cluster/1.2.12.Final is there any workaround? We too have the same issue configuring Jboss 7.1.1 and Apache httpd 2.4.12 with mod_cluster/1.3.1.Final (mod so files build from source) error seen in Jboss server log ============ 18:29:08,415 INFO [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) IO error sending command CONFIG to proxy server01/1.1.1.1:6666: java.net.SocketTimeoutException: Read timed out ============ The code fix provided in below link is already merged in mod_cluster/1.3.1.Final, but still issue remains https://developer.jboss.org/thread/231375?start=15&tstart=0 was (Author: mdelson): We too have the same issue configuring Jboss 7.1.1 and Apache httpd 2.4.12 with mod_cluster/1.3.1.Final (mod so files build from source) error seen in Jboss server log ============ 18:29:08,415 INFO [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) IO error sending command CONFIG to proxy server01/1.1.1.1:6666: java.net.SocketTimeoutException: Read timed out ============ The code fix provided in below link is already merged in mod_cluster/1.3.1.Final, but still issue remains https://developer.jboss.org/thread/231375?start=15&tstart=0 > SocketTimeoutException in DefaultMCMPHandler when using httpd 2.4.x > ------------------------------------------------------------------- > > Key: MODCLUSTER-353 > URL: https://issues.jboss.org/browse/MODCLUSTER-353 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.1.Final > Environment: httpd-2.4.6 and mod_cluster-1.2.1.Final and above > Reporter: Marco Danti > Assignee: Jean-Frederic Clere > Attachments: screenshot-1.png > > > After upgrading a web server from Apache 2.2.x (with mod_cluster 1.2.0) to Apache 2.4.6 (with mod_cluster 1.2.1.Final), when I bring up JBoss (7.2.0.Final) I start seeing repeated errors like the following: > > 14:45:36,777 INFO [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) IO error sending command CONFIG to proxy stw-1.priv.softeco.it/172.16.0.133:6666: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) [rt.jar:1.7.0_21] > at java.net.SocketInputStream.read(SocketInputStream.java:150) [rt.jar:1.7.0_21] > at java.net.SocketInputStream.read(SocketInputStream.java:121) [rt.jar:1.7.0_21] > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) [rt.jar:1.7.0_21] > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) [rt.jar:1.7.0_21] > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) [rt.jar:1.7.0_21] > at java.io.InputStreamReader.read(InputStreamReader.java:184) [rt.jar:1.7.0_21] > at java.io.BufferedReader.fill(BufferedReader.java:154) [rt.jar:1.7.0_21] > at java.io.BufferedReader.readLine(BufferedReader.java:317) [rt.jar:1.7.0_21] > at java.io.BufferedReader.readLine(BufferedReader.java:382) [rt.jar:1.7.0_21] > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:670) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequests(DefaultMCMPHandler.java:437) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:385) > at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:349) > at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:468) > at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:244) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1323) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1588) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1574) [jbossweb-7.2.0.Final.jar:7.2.0.Final] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-475: ---------------------------------------------- Summary: Automate built artifacts release to GitHub Releases Key: MODCLUSTER-475 URL: https://issues.jboss.org/browse/MODCLUSTER-475 Project: mod_cluster Issue Type: Task Reporter: Michal Karm Babacek Assignee: Michal Karm Babacek 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-474) Provide means of having on-line editable, simple markup static documentation and FAQ presentation

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-474?page=com.atlassian.jira.pl... ] Michal Karm Babacek resolved MODCLUSTER-474. -------------------------------------------- Resolution: Done h3. [modcluster.io|http://modcluster.io/] * Jekyll generated static web page * content written in Markdown * uses GitHub's Git Large File Storage for released bits (1.3.1.Final now) * GitHub Pages for Jekyll SaaS hosting, i.e. one pushes Markdown and GitHub generates HTML from it * a substantial amount of former Docbook text ported (it's still work in progress) * all examples ported from former Github wiki page that is dead now * all release notes ported and enriched with links to releases and JIRA issues h3. Communication Furthermore, there is a new #mod_cluster IRC channel on Freenode and modcluster Slack team space. Slack is interlinked with IRC, so user's messages sent to IRC end up on our Slack and vise versa. This neatly solves the issue of off-line message delivery absent on IRC. See [modcluster.io|http://modcluster.io]'s left sidebar for links to channels. h3. Further steps * finish porting and re-organization of the [main documentation page|http://modcluster.io/documentation/] * create Undertow section and interlink it with the upstream Undertow documentation so as users have all Apache/Undertow mod_cluster capabilities descriptions reachable from a one place * add new examples and FAQ based on most frequent JBoss forums and Stackoverflow questions (an ongoing effort) * apart from Docker image for Apache HTTP Server, also create and promote pre-configured Tomcat images with mod_cluster * include Azure tutorial for configuring dynamic mod_cluster environment * include Tutum Docker tutorial for orchestration of many mod_cluster containers * include links to Fedora mod_cluster RPMs https://karm.fedorapeople.org/mod_cluster/ and pre-build these for major x86_64 Fedora releases * include reference to Circle CI nightly build of mod_cluster for Linux x86_64 > Provide means of having on-line editable, simple markup static documentation and FAQ presentation > ------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-474 > URL: https://issues.jboss.org/browse/MODCLUSTER-474 > Project: mod_cluster > Issue Type: Task > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Critical > Labels: documentation, ux > > h3. Requirements > * Markdown (or other simple markup) > * Statically generated > * outsourced hosting for web > * outsourced hosting for released bits -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-474) Provide means of having on-line editable, simple markup static documentation and FAQ presentation

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-474: ---------------------------------------------- Summary: Provide means of having on-line editable, simple markup static documentation and FAQ presentation Key: MODCLUSTER-474 URL: https://issues.jboss.org/browse/MODCLUSTER-474 Project: mod_cluster Issue Type: Task Reporter: Michal Karm Babacek Assignee: Michal Karm Babacek Priority: Critical h3. Requirements * Markdown (or other simple markup) * Statically generated * outsourced hosting for web * outsourced hosting for released bits -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues January 2016