January 2011 - 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

11 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

4
32
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

3
17
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

12 years, 2 months

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

12 years, 4 months

4
12
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-187) ModClusterListener not working with Embedded Tomcat 6

by Galder Zamarreño (JIRA)

ModClusterListener not working with Embedded Tomcat 6 ----------------------------------------------------- Key: MODCLUSTER-187 URL: https://jira.jboss.org/browse/MODCLUSTER-187 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Reporter: Galder Zamarreño Assignee: Jean-Frederic Clere ModClusterListener does not work with embedded Tomcat. The listener does not seem to get called and hence it does not connect to mod_cluster httpd proxy. -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-201) update mod_cluster to use HTTP/1.1

by Samuel Mendenhall (JIRA)

update mod_cluster to use HTTP/1.1 ---------------------------------- Key: MODCLUSTER-201 URL: https://issues.jboss.org/browse/MODCLUSTER-201 Project: mod_cluster Issue Type: Feature Request Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Priority: Minor 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-192) Add SSL stuff in the FAQ

by Jean-Frederic Clere (JIRA)

Add SSL stuff in the FAQ ------------------------ Key: MODCLUSTER-192 URL: https://jira.jboss.org/browse/MODCLUSTER-192 Project: mod_cluster Issue Type: Feature Request Environment: docs Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere we need something like: openssl pkcs12 -export -nokeys -in /home/jfclere/CA/cacert.pem -out ca.p12 because nothing explains how the ca.p12 is created. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-191) JBoss Enterprise Application Platform * JBPAPP-5315 mod_cluster: proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed

by Jean-Frederic Clere (JIRA)

JBoss Enterprise Application Platform * JBPAPP-5315 mod_cluster: proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed -------------------------------------------------------------------------------------------------------------------------- Key: MODCLUSTER-191 URL: https://jira.jboss.org/browse/MODCLUSTER-191 Project: mod_cluster Issue Type: Bug Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere The problem is the following: +++ [Wed Oct 27 11:33:30 2010] [error] ajp_cping_cpong: apr_socket_recv failed [Wed Oct 27 11:33:30 2010] [debug] mod_proxy_cluster.c(1213): ajp_cping_cpong: Done [Wed Oct 27 11:33:30 2010] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (127.0.0.1) +++ and later: +++ [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4) [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data [Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 [Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09 [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(543): proxy: Processing of request failed backend: 1, output: 0 [Wed Oct 27 11:33:55 2010] [error] proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed +++ And the node is marked broken for a while, until: +++ Wed Oct 27 11:35:00 2010] [debug] proxy_util.c(1955): proxy: ajp: worker for (127.0.0.1) has been marked for retry +++ The STATUS should be able to restore the node and may be the answer 09 should not be taken as broken node error: it is just a broken socket error. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-194) When encrypting the mod_cluster traffic, can't use the http connector

by Samuel Mendenhall (JIRA)

When encrypting the mod_cluster traffic, can't use the http connector --------------------------------------------------------------------- Key: MODCLUSTER-194 URL: https://jira.jboss.org/browse/MODCLUSTER-194 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.Final Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Priority: Minor It would appear not possible to use the http connector when encrypting the mod_cluster connection. For mod_cluster to use the 8443 connector in JBoss, one has to comment out both the 8009 connector and 8080. But this raises a question, even if it were possible to keep the 8080 connector, it doesn't appear mod_cluster is able to hit both, as there would need to be multiple mod_cluster VHs in httpd. -- 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, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues January 2011