November 2011 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-267) String index out of range: -1 with a lot of nodes/deployments

by Yves Peter (Created) (JIRA)

String index out of range: -1 with a lot of nodes/deployments ------------------------------------------------------------- Key: MODCLUSTER-267 URL: https://issues.jboss.org/browse/MODCLUSTER-267 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final, 1.1.2.Final , 1.1.1.Final Environment: Centos Linux 5.4 32 Bit x86 JBoss 5.1 & JBoss 7 mod_cluster-1.1.3.Final-bin mod_cluster-1.1.3.Final-linux2-x86-ssl Reporter: Yves Peter Assignee: Jean-Frederic Clere With mod_cluster Version 1.1.1 an up when there are already lot of application servers registered and a new server trys to register on mod_cluster the following error gets thrown on the server: 2011-09-20 09:10:34,759 INFO [org.jboss.modcluster.ModClusterService] (main) Initializing mod_cluster 1.1.3.Final 2011-09-20 09:10:34,855 DEBUG [org.jboss.modcluster.ModClusterService] (main) Received server start event 2011-09-20 09:10:45,107 DEBUG [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Check status for engine [jboss.web] 2011-09-20 09:10:45,108 TRACE [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Sending command [org.jboss.modcluster.mcmp.impl.DefaultMCMPRequest{requestType=INFO,wildcard=false,jvmRoute=null,parameters={}}] to proxy [jsplb01x.umobi.mobicorp.test/10.32.34.139:80] 2011-09-20 09:10:45,111 TRACE [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Parsing responseStatus:HTTP/1.1 200 OK 2011-09-20 09:10:45,133 TRACE [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) [org.jboss.modcluster.mcmp.impl.DefaultMCMPRequest{requestType=CONFIG,wildcard=false,jvmRoute=defaultmetro_u_01,parameters={Balancer=defaultmetro, Host=10.32.34.70, Maxattempts=1, Port=8009, Type=ajp}}, org.jboss.modcluster.mcmp.impl.DefaultMCMPRequest{requestType=ENABLE-APP,wildcard=false,jvmRoute=defaultmetro_u_01,parameters={Alias=localhost, Context=/blublu/sampleApp}}] 2011-09-20 09:10:45,134 TRACE [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Sending command [org.jboss.modcluster.mcmp.impl.DefaultMCMPRequest{requestType=CONFIG,wildcard=false,jvmRoute=defaultmetro_u_01,parameters={Balancer=defaultmetro, Host=10.32.34.70, Maxattempts=1, Port=8009, Type=ajp}}] to proxy [jsplb01x.umobi.mobicorp.test/10.32.34.139:80] 2011-09-20 09:10:45,134 TRACE [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Parsing responseStatus:1f53 2011-09-20 09:10:45,134 INFO [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Error parsing response header for command CONFIG java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1937) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequest(DefaultMCMPHandler.java:667) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.sendRequests(DefaultMCMPHandler.java:476) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:417) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:377) at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:480) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:323) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1348) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1612) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1601) at java.lang.Thread.run(Thread.java:619) 2011-09-20 09:10:45,135 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Error [null: null: {4}] sending command CONFIG to proxy jsplb01x.umobi.mobicorp.test/10.32.34.139:80, configuration will be reset 2011-09-20 09:10:55,523 DEBUG [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Check status for engine [jboss.web] -- 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

8
12
0 / 0

[JBoss JIRA] (MODCLUSTER-266) warning while compiling on some lab boxes

by Jean-Frederic Clere (Created) (JIRA)

warning while compiling on some lab boxes ----------------------------------------- Key: MODCLUSTER-266 URL: https://issues.jboss.org/browse/MODCLUSTER-266 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor size_t != int on any platform (on 64-bit its usually 64) However think you are not using +2G sizes. However it might break on negative values due to unsigned int64 -> int32 conversion. .\mod_proxy_cluster.c(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data .\mod_proxy_cluster.c(1026) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data .\mod_proxy_cluster.c(1020) : warning C4101: 'name' : unreferenced local variable .\mod_proxy_cluster.c(1092) : warning C4101: 'ret' : unreferenced local variable .\mod_proxy_cluster.c(1225) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data .\mod_proxy_cluster.c(1226) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data .\mod_proxy_cluster.c(1910) : warning C4244: 'return' : conversion from '__int64' to 'int', possible loss of data .\mod_proxy_cluster.c(2040) : warning C4267: 'function' : conversion from 'size_t' to 'int', possible loss of data -- 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
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-231) mod_cluster forgets removed node too fast

by Radoslav Husar (JIRA)

mod_cluster forgets removed node too fast ----------------------------------------- Key: MODCLUSTER-231 URL: https://issues.jboss.org/browse/MODCLUSTER-231 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.0.10 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Minor See JBPAPP-6326. WAITFORREMOVE should be configurable (as it is currently hardcoded to be 10 seconds). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-250) bad interaction with ProxyPassReverse when redirection.

by Jean-Frederic Clere (JIRA)

bad interaction with ProxyPassReverse when redirection. ------------------------------------------------------- Key: MODCLUSTER-250 URL: https://issues.jboss.org/browse/MODCLUSTER-250 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final Environment: Mixing ProxyPass/ProxyPassReverse and mod_cluster Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.4.Final Using: ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On ProxyPassReverse / balancer://mycluster/ or ProxyPass / balancer://mycluster stickysession=JSESSIONID|jsessionid nofailover=On ProxyPassReverse / balancer://mycluster (note that this one won't work with mod_proxy_balancer). You get stuff like: curl -v http://jfcpc:8000/myapp +++ < HTTP/1.1 302 Moved Temporarily < Date: Thu, 25 Aug 2011 09:40:17 GMT < Server: Apache-Coyote/1.1 < Location: http://jfcpc:8000//myapp/ < Content-Length: 0 < Content-Type: text/plain +++ Or curl -v http://jfcpc:8000/myapp/TestRedirect?location=/toto.html +++ < HTTP/1.1 302 Moved Temporarily < Date: Thu, 25 Aug 2011 09:42:59 GMT < Server: Apache-Coyote/1.1 < Location: http://jfcpc:8000//toto.html;jsessionid=OYeoix8WaRh6VEtlSrfzIS7Q.498bb1f0... < Content-Length: 0 < Set-Cookie: JSESSIONID=OYeoix8WaRh6VEtlSrfzIS7Q.498bb1f0-00d9-3436-a341-7f012bc2e7ec; Path=/myapp < Content-Type: text/plain +++ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-261) segmentation fault with nofailover=On and proxy in virtual host

by Tomas Huryn (JIRA)

segmentation fault with nofailover=On and proxy in virtual host --------------------------------------------------------------- Key: MODCLUSTER-261 URL: https://issues.jboss.org/browse/MODCLUSTER-261 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final Environment: RHEL 5.7, Apache HTTPD 2.2.3 (packaged) or Apache HTTPD 2.2.21 (compiled), EAP 5.1.1 Reporter: Tomas Huryn Assignee: Jean-Frederic Clere Priority: Blocker we have - two clusters (2 JBoss instances for cluster1 (inst1 and inst2), 1 JBoss instance for cluster2 (inst3)). All instances run on the same machine (as) with binding manager - AJP on JBoss (port 8009 (inst1), 8109 (inst2), 8209 (inst3)) - root context enabled, application is in ROOT.war - defined jvmRoute in server.xml (inst1 -Djboss.web.jvmRoute=as.jb1 , inst2 -Djboss.web.jvmRoute=as.jb2 , inst3 -Djboss.web.jvmRoute=as.cms1) - Apache HTTPD runs on separate machine (ws) we need - cluster1 has connection to inst1 and inst2 with sticky session (client with one session will be routed to one instance only) - cluster2 has connection to inst3 We had tryed 2 solutions with no success: SOLUTION 1 - all in virtual host <VirtualHost externalip:8080> ServerName web1 <Proxy balancer://cluster1/> Order deny,allow Allow from all BalancerMember ajp://as:8009/ route=as.jb1 BalancerMember ajp://as:8109/ route=as.jb2 </Proxy> ProxyPass / balancer://cluster1/ stickysession=JSESSIONID|jsessionid nofailover=On ProxyPassReverse / balancer://cluster1/ </VirtualHost> <VirtualHost externalip:8080> ServerName web2 <Proxy balancer://cluster2/> Order deny,allow Allow from all BalancerMember ajp://as:8209/ route=as.cms1 </Proxy> ProxyPass / balancer://cluster2/ stickysession=JSESSIONID|jsessionid nofailover=On ProxyPassReverse / balancer://cluster2/ </VirtualHost> Result: Solution generate segmentation fault in error log, where somebody try to browse web. If we remove nofailover=On, all works fine except stick session - requests are splited to inst1 and inst2. SOLUTION2 - apache wide configuration <Proxy balancer://cluster1/> Order deny,allow Allow from all BalancerMember ajp://as:8009/ route=as.jb1 BalancerMember ajp://as:8109/ route=as.jb2 </Proxy> <Proxy balancer://cluster2/> Order deny,allow Allow from all BalancerMember ajp://as:8209/ route=as.cms1 </Proxy> <VirtualHost externalip:8080> ServerName web1 ProxyPass / balancer://cluster1/ stickysession=JSESSIONID|jsessionid nofailover=On ProxyPassReverse / balancer://cluster1/ </VirtualHost> <VirtualHost externalip:8080> ServerName web2 ProxyPass / balancer://cluster2/ stickysession=JSESSIONID|jsessionid nofailover=On ProxyPassReverse / balancer://cluster2/ </VirtualHost> Result: Sticky session works fine (no segmentation fault), but requests for web1 is routed to inst3 (cluster2) too and requests for web2 is routed to inst1 (cluster1) too. So there is problem with existence of two proxy cluster conffiguration directive. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-258) Error 503 using mod_cluster

by Jean-Frederic Clere (JIRA)

Error 503 using mod_cluster --------------------------- Key: MODCLUSTER-258 URL: https://issues.jboss.org/browse/MODCLUSTER-258 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final, MOD_CLUSTER_1_0_10_GA_CP02 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Blocker Fix For: MOD_CLUSTER_1_0_10_GA_CP03, 1.1.4.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-252) routing table lookup creates performance issues.

by Jean-Frederic Clere (JIRA)

routing table lookup creates performance issues. ------------------------------------------------ Key: MODCLUSTER-252 URL: https://issues.jboss.org/browse/MODCLUSTER-252 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final, MOD_CLUSTER_1_0_10_GA_CP02 Environment: use ~ 200 workers Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: MOD_CLUSTER_1_0_10_GA_CP03, 1.1.4.Final the throughput goes down to ~ 5 req/s -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-246) :read-attribute and :write-attribute Error in AS7

by Stefan Negrea (JIRA)

:read-attribute and :write-attribute Error in AS7 ------------------------------------------------- Key: MODCLUSTER-246 URL: https://issues.jboss.org/browse/MODCLUSTER-246 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.3.Final Reporter: Stefan Negrea Assignee: Jean-Frederic Clere :read-attribute(name=xyz) and :write-attribute(name=xyz,value=zyx) do not work in console with JBoss AS7.1 nightly builds. The expectation is that :read-attribute will return the current value of the property or the default value if the property has not been set. For :write-attribute the expectation is that all the properties listed in :read-resource-description can be set. The JBoss was started with the following command: bin/standalone.sh --server-config=standalone-ha.xml Here is the current output for invoking the two operations use the advertise attribute as an example. The outcome of both operations is failed. [standalone@localhost:9999 subsystem=modcluster] :read-attribute(name=advertise) { "outcome" => "failed", "failure-description" => "No known attribute advertise", "rolled-back" => true } [standalone@localhost:9999 subsystem=modcluster] :write-attribute(name=advertise,value=true) { "outcome" => "failed", "failure-description" => "No known attribute called advertise", "rolled-back" => true } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-236) Allow context lengths greater than 40

by Samuel Mendenhall (JIRA)

Allow context lengths greater than 40 ------------------------------------- Key: MODCLUSTER-236 URL: https://issues.jboss.org/browse/MODCLUSTER-236 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.2.Final Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.1.3.Final The mod_cluster 1.1 documentation states the following in the Limitation section: "Max context length 40 (for example myapp.war deploys in /myapp /myapp is the context)." This value should be at least doubled to 80 for use with ESB which creates long context names. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-245) Calculate the MAXMESSSIZE dynamically

by Samuel Mendenhall (JIRA)

Calculate the MAXMESSSIZE dynamically ------------------------------------- Key: MODCLUSTER-245 URL: https://issues.jboss.org/browse/MODCLUSTER-245 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.2.Final Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.1.3.Final Calculate the MAXMESSIZE dynamically at start time from the rest of the configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues November 2011