May 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-376?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-376 started by Michal Karm Babacek. ------------------------------------------------------ > multiple workers with the same id following a tomcat crash/kill > --------------------------------------------------------------- > > Key: MODCLUSTER-376 > URL: https://issues.jboss.org/browse/MODCLUSTER-376 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.0.10, 1.2.11.Final > Environment: -JBoss Enterprise Web Server 1.0.2 > -mod_cluster 1.0.10.GA_CP04 > -Red Hat Enterprise Linux 5 > Reporter: Aaron Ogburn > Assignee: Michal Karm Babacek > Fix For: 1.2.13.Final > > Attachments: 131122.patch > > > Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker. > The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination. Thus the ping fails, and load factor is not applied. The persistent -1 load state leads to 503s. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-376) multiple workers with the same id following a tomcat crash/kill

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-376?page=com.atlassian.jira.pl... ] Michal Karm Babacek reassigned MODCLUSTER-376: ---------------------------------------------- Assignee: Jean-Frederic Clere (was: Michal Karm Babacek) > multiple workers with the same id following a tomcat crash/kill > --------------------------------------------------------------- > > Key: MODCLUSTER-376 > URL: https://issues.jboss.org/browse/MODCLUSTER-376 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.0.10, 1.2.11.Final > Environment: -JBoss Enterprise Web Server 1.0.2 > -mod_cluster 1.0.10.GA_CP04 > -Red Hat Enterprise Linux 5 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.13.Final > > Attachments: 131122.patch > > > Following a kill or crash of tomcat, multiple workers are seen for a single id when a new tomcat node reconnects and reuses the id from the previously crashed worker. > The STATUS's ping check sees the old crashed worker first for the id and so pings the wrong destination. Thus the ping fails, and load factor is not applied. The persistent -1 load state leads to 503s. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-501: ------------------------------------------- Fix Version/s: 1.3.3.Final > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.3.Final > > Attachments: vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-507) Worker22 on RHEL-7 [mod_cluster segfaults]

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-507: ---------------------------------------------- Summary: Worker22 on RHEL-7 [mod_cluster segfaults] Key: MODCLUSTER-507 URL: https://issues.jboss.org/browse/MODCLUSTER-507 Project: mod_cluster Issue Type: Bug Components: Native (httpd modules) Affects Versions: 1.2.9.Final Environment: mod_cluster-1.3.2 *IS NOT* affected any more Reporter: Michal Karm Babacek Assignee: Jean-Frederic Clere Fix For: 1.2.13.Final Long term (days) running on httpd 2.2.26, with *worker* MPM on RHEL 7 x86_64, random segfaults in mod_manager. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-506) SegFault due to corrupt nodestatsmem

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-506: ---------------------------------------------- Summary: SegFault due to corrupt nodestatsmem Key: MODCLUSTER-506 URL: https://issues.jboss.org/browse/MODCLUSTER-506 Project: mod_cluster Issue Type: Bug Components: Native (httpd modules) Affects Versions: 1.2.12.Final Environment: _redhat_2.ep6.el6.x86_64 Reporter: Michal Karm Babacek Assignee: Jean-Frederic Clere Fix For: 1.2.13.Final See linked bugzillas, corrupted nodestatsmem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-437) Misleading mod_cluster error log : All workers are in error state

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-437?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-437: ------------------------------------------- Fix Version/s: 1.2.13.Final > Misleading mod_cluster error log : All workers are in error state > ----------------------------------------------------------------- > > Key: MODCLUSTER-437 > URL: https://issues.jboss.org/browse/MODCLUSTER-437 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.2.13.Final > > > See [BZ 995345|https://bugzilla.redhat.com/show_bug.cgi?id=995345] for details. > IMHO this is a minor usability fix that might help users to better understand the log, but it's not anything crucial. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-292) Use "MulticastSocket(SocketAddress bindaddr)" on Solaris

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-292?page=com.atlassian.jira.pl... ] Radoslav Husar edited comment on MODCLUSTER-292 at 5/30/16 5:18 PM: -------------------------------------------------------------------- JGroups as of commit 3a47b9174b02bdccf5a382c585f4a42d64bebe93 [1] also binds to mcast address on Mac OS X, the current logic is: {noformat} can_bind_to_mcast_addr=(Util.checkForLinux() && !Util.checkForAndroid()) || Util.checkForSolaris() || Util.checkForHp() || Util.checkForMac(); {noformat} [1] https://github.com/belaban/JGroups/commit/3a47b9174b02bdccf5a382c585f4a42... was (Author: rhusar): JGroups as of commit 6359e3fbfbc82967ad1d45f12f9f4b9145419911 also binds to mcast address on Mac OS X, the current logic is: {noformat} can_bind_to_mcast_addr=(Util.checkForLinux() && !Util.checkForAndroid()) || Util.checkForSolaris() || Util.checkForHp() || Util.checkForMac(); {noformat} > Use "MulticastSocket(SocketAddress bindaddr)" on Solaris > -------------------------------------------------------- > > Key: MODCLUSTER-292 > URL: https://issues.jboss.org/browse/MODCLUSTER-292 > Project: mod_cluster > Issue Type: Task > Affects Versions: 1.2.0.Final > Reporter: Brian Stansberry > Assignee: Radoslav Husar > > MulticastSocketFactoryImpl determines whether it can use the "MulticastSocket(SocketAddress bindaddr)" constructor variant based on this: > this.linuxlike = (value != null) && (value.toLowerCase().startsWith("linux") || value.toLowerCase().startsWith("mac") || value.toLowerCase().startsWith("hp")); > JGroups when doing a similiar test also allows Solaris via including (value.toLowerCase().startsWith("sun") in the test. > (Tangent: JGroups doesn't allow "mac", which sounds like a good topic for discussion between the respective teams.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-292) Use "MulticastSocket(SocketAddress bindaddr)" on Solaris

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-292?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-292: ------------------------------------------- JGroups as of commit 6359e3fbfbc82967ad1d45f12f9f4b9145419911 also binds to mcast address on Mac OS X, the current logic is: {noformat} can_bind_to_mcast_addr=(Util.checkForLinux() && !Util.checkForAndroid()) || Util.checkForSolaris() || Util.checkForHp() || Util.checkForMac(); {noformat} > Use "MulticastSocket(SocketAddress bindaddr)" on Solaris > -------------------------------------------------------- > > Key: MODCLUSTER-292 > URL: https://issues.jboss.org/browse/MODCLUSTER-292 > Project: mod_cluster > Issue Type: Task > Affects Versions: 1.2.0.Final > Reporter: Brian Stansberry > Assignee: Radoslav Husar > > MulticastSocketFactoryImpl determines whether it can use the "MulticastSocket(SocketAddress bindaddr)" constructor variant based on this: > this.linuxlike = (value != null) && (value.toLowerCase().startsWith("linux") || value.toLowerCase().startsWith("mac") || value.toLowerCase().startsWith("hp")); > JGroups when doing a similiar test also allows Solaris via including (value.toLowerCase().startsWith("sun") in the test. > (Tangent: JGroups doesn't allow "mac", which sounds like a good topic for discussion between the respective teams.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-292) Use "MulticastSocket(SocketAddress bindaddr)" on Solaris

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-292?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-292: ----------------------------------------- Assignee: Radoslav Husar (was: Jean-Frederic Clere) > Use "MulticastSocket(SocketAddress bindaddr)" on Solaris > -------------------------------------------------------- > > Key: MODCLUSTER-292 > URL: https://issues.jboss.org/browse/MODCLUSTER-292 > Project: mod_cluster > Issue Type: Task > Affects Versions: 1.2.0.Final > Reporter: Brian Stansberry > Assignee: Radoslav Husar > > MulticastSocketFactoryImpl determines whether it can use the "MulticastSocket(SocketAddress bindaddr)" constructor variant based on this: > this.linuxlike = (value != null) && (value.toLowerCase().startsWith("linux") || value.toLowerCase().startsWith("mac") || value.toLowerCase().startsWith("hp")); > JGroups when doing a similiar test also allows Solaris via including (value.toLowerCase().startsWith("sun") in the test. > (Tangent: JGroups doesn't allow "mac", which sounds like a good topic for discussion between the respective teams.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[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 updated MODCLUSTER-397: ------------------------------------------- Fix Version/s: 1.2.13.Final > 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.3.Final, 1.2.13.Final > > > 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)

7 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 May 2016