August 2015 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-458) Add JVMRoute or node identifier to httpd/mod_cluster errors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-458?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-458: ---------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1258396|https://bugzilla.redhat.com/show_bug.cgi?id=1258396] from NEW to MODIFIED > Add JVMRoute or node identifier to httpd/mod_cluster errors > ----------------------------------------------------------- > > Key: MODCLUSTER-458 > URL: https://issues.jboss.org/browse/MODCLUSTER-458 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Reporter: Coty Sutherland > Assignee: Michal Karm Babacek > Fix For: 1.3.2.Alpha1 > > > Messages such as: > [Tue Apr 14 10:38:56 2015] [warn] manager_handler STATUS error: MEM: Can't read node > are very difficult to troubleshoot given the limited context provided. It would be great if we could add some sort of node identifier or the JVMRoute of the node to the message above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-466: ---------------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1256607|https://bugzilla.redhat.com/show_bug.cgi?id=1256607] from POST to MODIFIED > mod_cluster undersizes the connection pool on httpd 2.2 > ------------------------------------------------------- > > Key: MODCLUSTER-466 > URL: https://issues.jboss.org/browse/MODCLUSTER-466 > Project: mod_cluster > Issue Type: Bug > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.11.Final > > > If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like: > [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ... > Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-466: ------------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 1.2.11.Final Resolution: Done > mod_cluster undersizes the connection pool on httpd 2.2 > ------------------------------------------------------- > > Key: MODCLUSTER-466 > URL: https://issues.jboss.org/browse/MODCLUSTER-466 > Project: mod_cluster > Issue Type: Bug > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.11.Final > > > If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like: > [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ... > Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-466: ---------------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1256607|https://bugzilla.redhat.com/show_bug.cgi?id=1256607] from NEW to POST > mod_cluster undersizes the connection pool on httpd 2.2 > ------------------------------------------------------- > > Key: MODCLUSTER-466 > URL: https://issues.jboss.org/browse/MODCLUSTER-466 > Project: mod_cluster > Issue Type: Bug > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like: > [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ... > Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-467) ExcludedContexts are ignored if modcluster subsystem initialize before default-host

by Pierre-Luc Gregoire (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-467?page=com.atlassian.jira.pl... ] Pierre-Luc Gregoire edited comment on MODCLUSTER-467 at 8/27/15 12:04 PM: -------------------------------------------------------------------------- I have a fix using a system property to add a dependency on the desired host when the subsytem start. In ModClusterSubsystemAdd : .addDependency(ServiceName.parse("jboss.web.host.default-host")) where "jboss.web.host.default-host" could be a system property. Maybe not the best option but I tested it and it works well. This ensure that the host used in excludedContexts is initialized. However, this fix is for modcluster extension in JBoss 7.2 and I don't think there's an active branch for 7.2. I think this bug is still relevant since it's for modcluster 1.2.x and modcluster 1.2.x is for JBoss 7.2... right? Here is the link used to find how subsystem dependencies work : https://developer.jboss.org/message/776404#776404 was (Author: plgregoire): I will submit a fix using a system property to add a dependency on the desired host when the subsytem start. In ModClusterSubsystemAdd : .addDependency(ServiceName.parse("jboss.web.host.default-host")) where "jboss.web.host.default-host" could be a system property. Maybe not the best option but I tested it and it works well. This ensure that the host used in excludedContexts is initialized. Here is the link used to find how subsystem dependencies work. https://developer.jboss.org/message/776404#776404 > ExcludedContexts are ignored if modcluster subsystem initialize before default-host > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-467 > URL: https://issues.jboss.org/browse/MODCLUSTER-467 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final > Reporter: Pierre-Luc Gregoire > Assignee: Jean-Frederic Clere > Labels: jboss > > With JBoss 7.2.0.Final, modcluster will ignore excludedContexts defined in modcluster subsystem (ie jmx-console, ROOT). This is caused by engine.getHosts() not yet available when org.jboss.modcluster.ModClusterService.init(Server) try to setup his list of excludedContexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-467) ExcludedContexts are ignored if modcluster subsystem initialize before default-host

by Pierre-Luc Gregoire (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-467?page=com.atlassian.jira.pl... ] Pierre-Luc Gregoire commented on MODCLUSTER-467: ------------------------------------------------ Here is the link to download jmx-console.war for JBoss 7.2 : https://issues.jboss.org/browse/WFLY-1197 > ExcludedContexts are ignored if modcluster subsystem initialize before default-host > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-467 > URL: https://issues.jboss.org/browse/MODCLUSTER-467 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final > Reporter: Pierre-Luc Gregoire > Assignee: Jean-Frederic Clere > Labels: jboss > > With JBoss 7.2.0.Final, modcluster will ignore excludedContexts defined in modcluster subsystem (ie jmx-console, ROOT). This is caused by engine.getHosts() not yet available when org.jboss.modcluster.ModClusterService.init(Server) try to setup his list of excludedContexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-467) ExcludedContexts are ignored if modcluster subsystem initialize before default-host

by Pierre-Luc Gregoire (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-467?page=com.atlassian.jira.pl... ] Pierre-Luc Gregoire commented on MODCLUSTER-467: ------------------------------------------------ I will submit a fix using a system property to add a dependency on the desired host when the subsytem start. In ModClusterSubsystemAdd : .addDependency(ServiceName.parse("jboss.web.host.default-host")) where "jboss.web.host.default-host" could be a system property. Maybe not the best option but I tested it and it works well. This ensure that the host used in excludedContexts is initialized. Here is the link used to find how subsystem dependencies work. https://developer.jboss.org/message/776404#776404 > ExcludedContexts are ignored if modcluster subsystem initialize before default-host > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-467 > URL: https://issues.jboss.org/browse/MODCLUSTER-467 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.11.Final > Reporter: Pierre-Luc Gregoire > Assignee: Jean-Frederic Clere > Labels: jboss > > With JBoss 7.2.0.Final, modcluster will ignore excludedContexts defined in modcluster subsystem (ie jmx-console, ROOT). This is caused by engine.getHosts() not yet available when org.jboss.modcluster.ModClusterService.init(Server) try to setup his list of excludedContexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-467) ExcludedContexts are ignored if modcluster subsystem initialize before default-host

by Pierre-Luc Gregoire (JIRA)

Pierre-Luc Gregoire created MODCLUSTER-467: ---------------------------------------------- Summary: ExcludedContexts are ignored if modcluster subsystem initialize before default-host Key: MODCLUSTER-467 URL: https://issues.jboss.org/browse/MODCLUSTER-467 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.2.11.Final Reporter: Pierre-Luc Gregoire Assignee: Jean-Frederic Clere With JBoss 7.2.0.Final, modcluster will ignore excludedContexts defined in modcluster subsystem (ie jmx-console, ROOT). This is caused by engine.getHosts() not yet available when org.jboss.modcluster.ModClusterService.init(Server) try to setup his list of excludedContexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 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 updated MODCLUSTER-376: ------------------------------------------- Affects Version/s: 1.2.11.Final > 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 > 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.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated MODCLUSTER-466: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1256607, https://bugzilla.redhat.com/show_bug.cgi?id=1256608 > mod_cluster undersizes the connection pool on httpd 2.2 > ------------------------------------------------------- > > Key: MODCLUSTER-466 > URL: https://issues.jboss.org/browse/MODCLUSTER-466 > Project: mod_cluster > Issue Type: Bug > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like: > [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ... > Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2015