February 2012 - mod_cluster-issues

[JBoss JIRA] Created: (MODCLUSTER-160) Include link to mod_cluster config generator in publication mod_cluster User Guide.

by Gary Meintjes (JIRA)

Include link to mod_cluster config generator in publication mod_cluster User Guide. ----------------------------------------------------------------------------------- Key: MODCLUSTER-160 URL: https://jira.jboss.org/browse/MODCLUSTER-160 Project: mod_cluster Issue Type: Task Reporter: Gary Meintjes Assignee: Gary Meintjes Priority: Minor Insert a link in the publication to the mod_cluster configuration generating tool: http://lbconfig.appspot.com. Envisaged: Update trunk document for inclusion in EAP 5.1 release in August 2010. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-120) Apache with mod_cluster refuses to start at first, after 7 retries it starts up

by Radoslav Husar (JIRA)

Apache with mod_cluster refuses to start at first, after 7 retries it starts up ------------------------------------------------------------------------------- Key: MODCLUSTER-120 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-120 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: x64, RHEL 5, Server version: Apache/2.2.3, Server built: Jul 6 2009 05:29:28 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere When starting up Apache with mod cluster, by command: [hudson@perf10 httpd]$ /usr/sbin/apachectl -k start -d /tmp/hudson/httpd It refuses to start, but creates files in logs one-by-one and then when all files are created it accepts to start. [hudson@perf10 httpd]$ cat logs/error_log [Tue Jan 05 12:01:11 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:01:11 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:01:11 2010] [notice] Digest: done [Tue Jan 05 12:01:11 2010] [emerg] create_mem_node /tmp/hudson/httpd/logs/manager.node failed Configuration Failed [Tue Jan 05 12:01:37 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:01:37 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:01:37 2010] [notice] Digest: done [Tue Jan 05 12:01:37 2010] [emerg] create_mem_context failed Configuration Failed [Tue Jan 05 12:02:40 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:02:40 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:02:40 2010] [notice] Digest: done [Tue Jan 05 12:02:40 2010] [emerg] create_mem_host failed Configuration Failed [Tue Jan 05 12:04:43 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:04:43 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:04:43 2010] [notice] Digest: done [Tue Jan 05 12:04:43 2010] [emerg] create_mem_balancer failed Configuration Failed [Tue Jan 05 12:04:44 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:04:44 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:04:44 2010] [notice] Digest: done [Tue Jan 05 12:04:44 2010] [emerg] create_mem_sessionid failed Configuration Failed [Tue Jan 05 12:04:45 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:04:45 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:04:45 2010] [notice] Digest: done [Tue Jan 05 12:04:45 2010] [emerg] create_mem_domain failed Configuration Failed [Tue Jan 05 12:04:46 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Tue Jan 05 12:04:46 2010] [notice] Digest: generating secret for digest authentication ... [Tue Jan 05 12:04:46 2010] [notice] Digest: done [Tue Jan 05 12:04:46 2010] [notice] Advertise initialized for process 1713 [Tue Jan 05 12:04:46 2010] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations The configuration is here: https://svn.devel.redhat.com/repos/jboss-qa/load-testing/etc/httpd/mod_cl... Is there a workaround? What might be causing this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

4
32
0 / 0

[JBoss JIRA] (MODCLUSTER-264) jboss-admin.sh accepts crazy values for :add-proxy()

by Misty Stanley-Jones (Created) (JIRA)

jboss-admin.sh accepts crazy values for :add-proxy() ---------------------------------------------------- Key: MODCLUSTER-264 URL: https://issues.jboss.org/browse/MODCLUSTER-264 Project: mod_cluster Issue Type: Bug Environment: modcluster subsystem of AS 7.1 trunk Reporter: Misty Stanley-Jones Assignee: Jean-Frederic Clere I am allowed to use all of these kinds of syntax with :add-proxy(): [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123) { "outcome" => "success", "result" => { "domain-results" => {"step-1" => undefined}, "server-operations" => [{ "servers" => [], "operation" => { "address" => [("subsystem" => "modcluster")], "operation" => "add-proxy", "port" => 123, "host" => "abc.com", "operation-headers" => {"execute-for-coordinator" => true} } }] } } [domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com) { "outcome" => "success", "result" => { "domain-results" => {"step-1" => undefined}, "server-operations" => [{ "servers" => [], "operation" => { "address" => [("subsystem" => "modcluster")], "operation" => "add-proxy", "host" => "def.com", "operation-headers" => {"execute-for-coordinator" => true} } }] } } [domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999) { "outcome" => "success", "result" => { "domain-results" => {"step-1" => undefined}, "server-operations" => [{ "servers" => [], "operation" => { "address" => [("subsystem" => "modcluster")], "operation" => "add-proxy", "port" => 999, "operation-headers" => {"execute-for-coordinator" => true} } }] } } I think only the first one should be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

5
4
0 / 0

[JBoss JIRA] (MODCLUSTER-275) sticky session toggles randomly after the shutdown of the active node

by Christoph Gostner (Created) (JIRA)

sticky session toggles randomly after the shutdown of the active node --------------------------------------------------------------------- Key: MODCLUSTER-275 URL: https://issues.jboss.org/browse/MODCLUSTER-275 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.4.Final Reporter: Christoph Gostner Assignee: Jean-Frederic Clere Sticky session randomly toggles between cluster node after the shutdown of the active node. I'd expected that the session remains with one server only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address

by Jean-Frederic Clere (JIRA)

mod_cluster should use hostname provided in address instead a IP address ------------------------------------------------------------------------ Key: MODCLUSTER-168 URL: https://jira.jboss.org/browse/MODCLUSTER-168 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.CR3 Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere The CONFIG message contains something like: JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp Even if the Connector is defined like: <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" /> There are 2 ways to fix: - Use the String (Change the Connector.java in mod_cluster). - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
17
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-260) Move mod_cluster to Git / GitHub

by Radoslav Husar (JIRA)

Move mod_cluster to Git / GitHub -------------------------------- Key: MODCLUSTER-260 URL: https://issues.jboss.org/browse/MODCLUSTER-260 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.3.Final, 1.0.11 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Critical Sounds like a good idea to move over to GitHub. This will significantly help contribution form the community. This will also include creating engineering git repository for prod branches. Even projects like JGroups already miraculously moved to github :-) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
11
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-140) Rpc failure can lead to failure to deploy a webapp

by Paul Ferraro (JIRA)

Rpc failure can lead to failure to deploy a webapp -------------------------------------------------- Key: MODCLUSTER-140 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-140 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.CR1, 1.0.3.GA Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.0.4.GA, 1.1.0.CR2 An exception thrown during an rpc call should never propagate to the web container. See stack trace in forum thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-224) when using tomcat manager webapp to stop/start an application the start is ignored by mod_cluster

by Jean-Frederic Clere (JIRA)

when using tomcat manager webapp to stop/start an application the start is ignored by mod_cluster ------------------------------------------------------------------------------------------------- Key: MODCLUSTER-224 URL: https://issues.jboss.org/browse/MODCLUSTER-224 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.1.Final, 1.0.9 Environment: tomcat and manager webapp + any test webapp. Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.0.10, 1.1.2.Final See JBPAPP-6262 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
7
0 / 0

[JBoss JIRA] (MODCLUSTER-288) SystemMemoryUsageLoadMetric is of no use to anyone

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-288: ----------------------------------------- Summary: SystemMemoryUsageLoadMetric is of no use to anyone Key: MODCLUSTER-288 URL: https://issues.jboss.org/browse/MODCLUSTER-288 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Final, 1.1.1.Final, 1.1.0.Final, 1.0.10 Reporter: Michal Babacek Assignee: Paul Ferraro I am convinced that the [SystemMemoryUsageLoadMetric.java|https://github.com/modcluster/mod_cluste...] is of no use to anyone. I have tested it by allocating some memory outside the JVM control with [NativeMemoryStress.c|https://github.com/Karm/clusterbench/blob/system-mem...]. The results from Mod_cluster are such that the system is almost fully loaded all the time despite the fact that I work with 8GB RAM box with almost nothing running on it. This [picture|http://hudson.qa.jboss.com/hudson/view/mod_cluster-QE/view/mod_cl...] displays time on X axis and (100-(Load from Mod_cluster)) on Y axis. As you may observe, all 4 nodes appear to be under full load all the time and there is a spike on each of them. This spike represents a period of time when the aforementioned [NativeMemoryStress.c|https://github.com/Karm/clusterbench/blob/system-mem...] was called with the following setting: {noformat} megabytes 500; milliseconds 60000; {noformat} What had happened is that kernel has cleared some cache and garbage data from the RAM in order to accommodate new demands, so by the time I freed the memory, there was all of sudden actually more free RAM then before. The actual problem with the current [SystemMemoryUsageLoadMetric.java|https://github.com/modcluster/mod_cluste...] implementation using [OperatingSystemMXBean|http://docs.oracle.com/javase/6/docs/jre/api/manage...] is that this code: {code:lang=java} +++ public static final String FREE_MEMORY = "FreePhysicalMemorySize"; public static final String TOTAL_MEMORY = "TotalPhysicalMemorySize"; +++ double free = ((Number) this.server.getAttribute(name, FREE_MEMORY)).doubleValue(); double total = ((Number) this.server.getAttribute(name, TOTAL_MEMORY)).doubleValue(); return (total - free) / total; +++ {code} Is somewhat similar to this (on 8GB RAM machine with almost nothing running on at the moment): {noformat} [karm@killerbox karm]$ free -m total used free shared buffers cached Mem: 7933 6755 1177 0 44 141 -/+ buffers/cache: 6569 1363 Swap: 16383 58 16325 {noformat} Obviously, this does not mean that I could get only 1177MB of RAM if I want to. The "free" actually means "wasted". The majority of RAM is being used as cache. If I ask for e.g. 2GB, I am gonna get them, because kernel will simply sacrifice some cache, clears some garbage from RAM and free up space so as to accommodate my demands. So, according to my opinion, on a sane, well-behaving caching operating system, the [SystemMemoryUsageLoadMetric.java|https://github.com/modcluster/mod_cluste...] will always show ~ 98% RAM usage. Due to this fact, this metric is unlikely to be of some use to anyone. What do you think? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-91) Connector bind address of 0.0.0.0 propagated to proxy

by Brian Stansberry (JIRA)

Connector bind address of 0.0.0.0 propagated to proxy ----------------------------------------------------- Key: MODCLUSTER-91 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-91 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.1.GA Reporter: Brian Stansberry Assignee: Jean-Frederic Clere Marek Goldmann wrote: > I'm encountered a strange error. When I bind JBoss instance to 0.0.0.0 > address instead of a fixed ethernet address, node gets registered in > mod_cluster, shows in mod_cluster-manager, but every request to > registered contexts throws 503 error. > > httpd error log: > > [Fri Aug 07 03:21:05 2009] [error] (111)Connection refused: proxy: > ajp: attempt to connect to 0.0.0.0:8009 (0.0.0.0) failed > [Fri Aug 07 03:21:05 2009] [error] ap_proxy_connect_backend disabling > worker for (0.0.0.0) > [Fri Aug 07 03:21:15 2009] [error] proxy: ajp: disabled connection for > (0.0.0.0) > [Fri Aug 07 03:21:25 2009] [error] proxy: ajp: disabled connection for > (0.0.0.0) > > This looks like a bug for me, because many administrators are binding > JBoss to 0.0.0.0. The java side needs to understand that 0.0.0.0 is useless as a client address and send something useful. Trick is deciding what's useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues February 2012