July 2012 - mod_cluster-issues - Jboss List Archives

[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

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, 1 month

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, 1 month

5
4
0 / 0

[JBoss JIRA] (MODCLUSTER-306) Backport MODCLUSTER-201 to 1.0.10.GA - update mod_cluster to use HTTP/1.1

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-306: --------------------------------------- Summary: Backport MODCLUSTER-201 to 1.0.10.GA - update mod_cluster to use HTTP/1.1 Key: MODCLUSTER-306 URL: https://issues.jboss.org/browse/MODCLUSTER-306 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.Final Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.1.1.Final Certain technologies like siteminder require the host header which is not present in HTTP/1.0 so siteminder won't work out of the box with HTTP/1.0 -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] (MODCLUSTER-319) Backport MODCLUSTER-168 to 1.0.10.GA - mod_cluster should use hostname provided in address instead a IP address

by Aaron Ogburn (JIRA)

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] (MODCLUSTER-321) mod_cluster doesn't properly use timeouts in initial proxyList connection attempts

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-321: --------------------------------------- Summary: mod_cluster doesn't properly use timeouts in initial proxyList connection attempts Key: MODCLUSTER-321 URL: https://issues.jboss.org/browse/MODCLUSTER-321 Project: mod_cluster Issue Type: Bug Affects Versions: MOD_CLUSTER_1_0_10_GA_CP02 Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere Fix For: MOD_CLUSTER_1_0_10_GA_CP03 -- 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, 2 months

2
6
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

12 years, 2 months

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

12 years, 2 months

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

12 years, 2 months

4
11
0 / 0

[JBoss JIRA] (MODCLUSTER-315) Convert project to use i18n logging and exceptions

by James Perkins (JIRA)

James Perkins created MODCLUSTER-315: ---------------------------------------- Summary: Convert project to use i18n logging and exceptions Key: MODCLUSTER-315 URL: https://issues.jboss.org/browse/MODCLUSTER-315 Project: mod_cluster Issue Type: Task Reporter: James Perkins Assignee: Jean-Frederic Clere As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- 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, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues July 2012