January 2011 - mod_cluster-issues

[JBoss JIRA] Created: (MODCLUSTER-193) mod_cluster 1.1.0 docs step 11.1.4.3 is wrong

by Samuel Mendenhall (JIRA)

mod_cluster 1.1.0 docs step 11.1.4.3 is wrong --------------------------------------------- Key: MODCLUSTER-193 URL: https://jira.jboss.org/browse/MODCLUSTER-193 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.1.1.Final http://docs.jboss.org/mod_cluster/1.1.0/html/UsingSSL.html Section: 11.1.4.3. Create the client certificate Step 2 ================================== mkdir -p CERTS/Client cd CERTS/Client ================================== This is incorrect, it is the copy of step 1 instead of how to actually "Create a new request and sign it for the client certificate and key of the JBossWEB part." -- 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 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-200) Default maxAttempts set to -1 instead of 1

by Radoslav Husar (JIRA)

Default maxAttempts set to -1 instead of 1 ------------------------------------------ Key: MODCLUSTER-200 URL: https://issues.jboss.org/browse/MODCLUSTER-200 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.5, 1.0.4.GA Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.0.6 See JBPAPP-3724 - not fixed completely - only in HA MC Service, not in standard MC Service. The property in mod-cluster-jboss-beans.xml: <property name="maxAttempts">-1</property> The number of maximum attempts must be logically a natural number (it is impossible to attempt minus one times :-) The documentation claims the default value is 1. This is not in sync and can lead to confusion. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-173) Alias max length too low

by Gregory Lardiere (JIRA)

Alias max length too low ------------------------ Key: MODCLUSTER-173 URL: https://jira.jboss.org/browse/MODCLUSTER-173 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.3.GA Environment: Windows server 2008 Reporter: Gregory Lardiere Assignee: Jean-Frederic Clere We have virtual-hosts in server.xml with aliases of more than 40 characters. No problem on the jboss side, but on apache side, mod_cluster fails with the following message : "MEM: Can't read host alias". Changing HOSTALIASZ from 40 to 64 (mod_clustersize.h) resolves the problem (see patch #1). NB: I had to fix a few "NMAKEmakefile", otherwise it won't compile with Visual Studio 2010 (see patch #2) -- 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 months

4
11
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-204) Alias max length too low (255?)

by Jean-Frederic Clere (JIRA)

Alias max length too low (255?) ------------------------------- Key: MODCLUSTER-204 URL: https://issues.jboss.org/browse/MODCLUSTER-204 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.Final, 1.0.6 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor MODCLUSTER-173 was a request to increase to 100 but now we may need 255 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-190) mod_cluster issues an ENABLE-APP too early in the webapp lifecycle

by Samuel Mendenhall (JIRA)

mod_cluster issues an ENABLE-APP too early in the webapp lifecycle ------------------------------------------------------------------ Key: MODCLUSTER-190 URL: https://jira.jboss.org/browse/MODCLUSTER-190 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.4.GA Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.0.5 mod_cluster uses START_EVENT instead of a AFTER_START_EVENT so it might ENABLE the application too early. -- 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 months

3
8
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-203) CLONE - Quotes in jsessionId causing sticky sessions to fail

by Jean-Frederic Clere (JIRA)

CLONE - Quotes in jsessionId causing sticky sessions to fail ------------------------------------------------------------ Key: MODCLUSTER-203 URL: https://issues.jboss.org/browse/MODCLUSTER-203 Project: mod_cluster Issue Type: Bug Environment: JBoss 6 M2, mod_cluster's httpd Reporter: Wim Vandenhaute Assignee: Jean-Frederic Clere Fix For: 1.1.0.CR3 I am having an issue trying to setup sticky sessions for following configuration: 1 httpd front end 2 backend jboss instances What I am noticing is when running in a cluster, the JSESSIONID contains quotes like: Set-Cookie: JSESSIONID="DE0F7EEA2A5E90497D729DB27DDB4B25.192.168.7.11:8009:jboss.web"; Version=1; Path=/f00 Whilst not in a cluster: Set-Cookie: JSESSIONID=355F9E370912DC10187A15E8B02260CD; Path=/foo Now when I am looking in the httpd logging I see: mod_proxy_cluster.c(1681): cluster: Found value "54F0CFC4961C9ED14A64335B40645392.192.168.7.11:8009:jboss.web" for stickysession JSESSIONID In my opinion the quotes around the jsessionid is causing mod_proxy_cluster to fail in finding the jboss node to which to "stick" to. I recompiled mod_proxy_cluster with "HAVE_CLUSTER_EX_DEBUG" set for more debugging info and this confirmed my suspicion: mod_proxy_cluster.c(1739): find_nodedomain: finding node for 192.168.7.11:8009:jboss.web": mycluster mod_proxy_cluster.c(1752): find_nodedomain: finding domain for 192.168.7.11:8009:jboss.web": mycluster Looking in the code this shows that it was unable to find the node, due to the ending quote in the route. As for my JBoss Setup: * Uncommented ModClusterListener in jbossweb.sar/META-INF/jboss-beans.xml * mod_cluster.sar/META-INF/mod_cluster-jboss-beans.xml - changed ModClusterService to HAModClusterService - changed ${jboss.mod_cluster.advertise.enabled:false} to true As for my httpd setup: LoadModule proxy_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy.so LoadModule proxy_ajp_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_ajp.so LoadModule slotmem_module /opt/jboss/httpd/lib/httpd/modules/mod_slotmem.so LoadModule manager_module /opt/jboss/httpd/lib/httpd/modules/mod_manager.so LoadModule proxy_cluster_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_cluster.so LoadModule advertise_module /opt/jboss/httpd/lib/httpd/modules/mod_advertise.so LogLevel debug CreateBalancers 0 <VirtualHost *:80> <Location /mod_cluster-manager> SetHandler mod_cluster-manager Order deny,allow Deny from all Allow from all # Allow from 192.168.7. </Location> <Directory /> Order deny,allow Deny from all Allow from all </Directory> ProxyPass /foo balancer://mycluster/foo stickysession=JSESSIONID scolonpathdelim=On nofailover=On KeepAliveTimeout 60 MaxKeepAliveRequests 0 ManagerBalancerName mycluster AdvertiseFrequency 5 </VirtualHost> Listen sebeco-dev-11:443 <VirtualHost *:443> ServerName sebeco-dev-11:443 SSLEngine on SSLProxyEngine on SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL SSLCertificateFile "/opt/jboss/httpd/httpd/server.crt" SSLCertificateKeyFile "/opt/jboss/httpd/httpd/server.key" SSLCertificateChainFile "/opt/jboss/httpd/httpd/server-ca.crt" <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Location /> Order allow,deny Allow from all </Location> ProxyPass /foo balancer://mycluster/foo stickysession=JSESSIONID scolonpathdelim=On nofailover=On </VirtualHost> As my setup is not really complex at this point my gut says I am doing something wrong in the setup, but digging in the code shows the opposite. Any thougts? Best regards, Wim. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-202) the STATUS MCMP message is send before the connector is started

by Jean-Frederic Clere (JIRA)

the STATUS MCMP message is send before the connector is started --------------------------------------------------------------- Key: MODCLUSTER-202 URL: https://issues.jboss.org/browse/MODCLUSTER-202 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final, 1.0.5 Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor If you have an application slow to start the STATUS messages are sent before the connectors are started which causes error messages to be written in the log. Additionally that can delay the availability of the application to httpd. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues January 2011