[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-267) String index out of range: -1 with a lot of nodes/deployments
Radoslav Husar (Commented) (JIRA)
jira-events at lists.jboss.org
Tue Nov 8 07:13:45 EST 2011
[ https://issues.jboss.org/browse/MODCLUSTER-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641039#comment-12641039 ]
Radoslav Husar commented on MODCLUSTER-267:
-------------------------------------------
Yves analyzed that the messages from the server are malformed like this:
http://community.jboss.org/message/635423#635423
{code}
Re: Upgrade to 1.1.3 and Index out of range: -1
I did a TCPdump of the traffic between httpd and the JBoss and you can see that with enough nodes/deployments httpd starts to add some extra characters to it's response and the JBoss fails to parse it.
Here is what http sends on response to an INFO from JBoss:
HTTP/1.1 200 OK
Date: Tue, 20 Sep 2011 11:32:59 GMT
Server: Apache
Vary: Accept-Encoding
Keep-Alive: timeout=10
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/plain
1f82
Node: [1],Name: tariffing_def_x_01,Balancer: tariffing_def,LBGroup: ,Host: 10.32.34.58,Port: 8009,Type: ajp,Flushpackets: Off,Flushwait: 10,Ping: 10,Smax: 61,Ttl: 60,Elected: 0,Read: 0,Transfered: 0,Connected: 0,Load: 91
Node: [2],Name: ta...
You can see that the first thing after the headers is some random string: 1f82.
{code}
> 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.1.Final, 1.1.2.Final , 1.1.3.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
More information about the mod_cluster-issues
mailing list