July 2013 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-349) mod_manager truncates ENABLE-APP messages

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-349?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-349: ------------------------------------ Affects Version/s: 1.2.4.Final > mod_manager truncates ENABLE-APP messages > ----------------------------------------- > > Key: MODCLUSTER-349 > URL: https://issues.jboss.org/browse/MODCLUSTER-349 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04, 1.2.4.Final > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: ModCluster349.java, mod_cluster.patch > > > With lots of aliases, ENABLE-APP messages can be big enough to span several IP packets. > Sometimes, mod_manager will read only the first packet. > The message is therefore incomplete and mod_cluster configuration ends up corrupted : some aliases are missing and the context-root is replaced by "/". > This is caused by a wrong usage of ap_get_brigade() : it's called only once whereas it should be called until there's nothing left to read (see the attached patch). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-349) mod_manager truncates ENABLE-APP messages

by Gregory Lardiere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-349?page=com.atlassian.jira.pl... ] Gregory Lardiere commented on MODCLUSTER-349: --------------------------------------------- To reproduce the bug, run the attached Java class on a working mod_cluster setup : {code}java ModCluster349 <apache_hostname> <port> <jvmRoute> split{code} You can see on the status page that the context root "/" has been added (instead of "/ModCluster349") with a incomplete alias list. On the other hand, if you run : {code}java ModCluster349 <apache_hostname> <port> <jvmRoute>{code} then the context-root "/ModCluster349" is correctly added and the alias list is complete. > mod_manager truncates ENABLE-APP messages > ----------------------------------------- > > Key: MODCLUSTER-349 > URL: https://issues.jboss.org/browse/MODCLUSTER-349 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: ModCluster349.java, mod_cluster.patch > > > With lots of aliases, ENABLE-APP messages can be big enough to span several IP packets. > Sometimes, mod_manager will read only the first packet. > The message is therefore incomplete and mod_cluster configuration ends up corrupted : some aliases are missing and the context-root is replaced by "/". > This is caused by a wrong usage of ap_get_brigade() : it's called only once whereas it should be called until there's nothing left to read (see the attached patch). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-349) mod_manager truncates ENABLE-APP messages

by Gregory Lardiere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-349?page=com.atlassian.jira.pl... ] Gregory Lardiere updated MODCLUSTER-349: ---------------------------------------- Attachment: ModCluster349.java Test case > mod_manager truncates ENABLE-APP messages > ----------------------------------------- > > Key: MODCLUSTER-349 > URL: https://issues.jboss.org/browse/MODCLUSTER-349 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: ModCluster349.java, mod_cluster.patch > > > With lots of aliases, ENABLE-APP messages can be big enough to span several IP packets. > Sometimes, mod_manager will read only the first packet. > The message is therefore incomplete and mod_cluster configuration ends up corrupted : some aliases are missing and the context-root is replaced by "/". > This is caused by a wrong usage of ap_get_brigade() : it's called only once whereas it should be called until there's nothing left to read (see the attached patch). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-350) Optimize mod_cluster for high worker counts

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-350: --------------------------------------- Summary: Optimize mod_cluster for high worker counts Key: MODCLUSTER-350 URL: https://issues.jboss.org/browse/MODCLUSTER-350 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.2.4.Final Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere Performance degrades (increased load, longer responses) with increased worker counts on mod_cluster. It'd be nice if some optimizing could be done here so that workers are selected through hashes for better scaling. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-348) DefaultMCMPHandler can't handle chunked-encoding

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-348?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-348 at 7/25/13 12:04 PM: -------------------------------------------------------------------------- Back porting shouldn't be a problem. If you are using a supported version you should report the problem in the support system too. Otherwise I will patch the code and you will have to build it. was (Author: jfclere): Back shouldn't be a problem. If you are using a supported version you should do report it in the support system too. Otherwise I will patch the code and you will have to build it. > DefaultMCMPHandler can't handle chunked-encoding > ------------------------------------------------ > > Key: MODCLUSTER-348 > URL: https://issues.jboss.org/browse/MODCLUSTER-348 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: chunked.log > > > DefaultMCMPHandler send MCMP requests to mod_manager with HTTP version 1.1, but it can't understand chunked-encoded responses. Chunked encoding is mandatory in HTTP 1.1 (RFC2616 3.6.1). > With lots of nodes, contexts and aliases, the INFO command can return a chunked-encoded response. Then, every STATUS command will fail with a NumberFormatException (cf log). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-348) DefaultMCMPHandler can't handle chunked-encoding

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-348?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-348: ------------------------------------------------ Back shouldn't be a problem. If you are using a supported version you should do report it in the support system too. Otherwise I will patch the code and you will have to build it. > DefaultMCMPHandler can't handle chunked-encoding > ------------------------------------------------ > > Key: MODCLUSTER-348 > URL: https://issues.jboss.org/browse/MODCLUSTER-348 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: chunked.log > > > DefaultMCMPHandler send MCMP requests to mod_manager with HTTP version 1.1, but it can't understand chunked-encoded responses. Chunked encoding is mandatory in HTTP 1.1 (RFC2616 3.6.1). > With lots of nodes, contexts and aliases, the INFO command can return a chunked-encoded response. Then, every STATUS command will fail with a NumberFormatException (cf log). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

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

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-267?page=com.atlassian.jira.pl... ] Jean-Frederic Clere edited comment on MODCLUSTER-267 at 7/25/13 11:44 AM: -------------------------------------------------------------------------- See 63adf0c4186d890763aa3a9ac08310b26ec971f3 and 0c42501a099ef8192924ee2f805491d8d6f57355 (they need to be back ported to CP10. was (Author: jfclere): See 63adf0c4186d890763aa3a9ac08310b26ec971f3 and 0c42501a099ef8192924ee2f805491d8d6f57355 > 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 > Fix For: 1.2.0.Beta4 > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-348) DefaultMCMPHandler can't handle chunked-encoding

by Gregory Lardiere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-348?page=com.atlassian.jira.pl... ] Gregory Lardiere commented on MODCLUSTER-348: --------------------------------------------- Sorry for the duplicate, I didn't see the issue was already reported. Still, the problem isn't solved for the 1.0.x branch. Could you backport the fix, please? > DefaultMCMPHandler can't handle chunked-encoding > ------------------------------------------------ > > Key: MODCLUSTER-348 > URL: https://issues.jboss.org/browse/MODCLUSTER-348 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: chunked.log > > > DefaultMCMPHandler send MCMP requests to mod_manager with HTTP version 1.1, but it can't understand chunked-encoded responses. Chunked encoding is mandatory in HTTP 1.1 (RFC2616 3.6.1). > With lots of nodes, contexts and aliases, the INFO command can return a chunked-encoded response. Then, every STATUS command will fail with a NumberFormatException (cf log). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

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

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-267?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-267: ------------------------------------------------ See 63adf0c4186d890763aa3a9ac08310b26ec971f3 and 0c42501a099ef8192924ee2f805491d8d6f57355 > 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 > Fix For: 1.2.0.Beta4 > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-348) DefaultMCMPHandler can't handle chunked-encoding

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-348?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-348. -------------------------------------------- Resolution: Duplicate Issue See MODCLUSTER-267 > DefaultMCMPHandler can't handle chunked-encoding > ------------------------------------------------ > > Key: MODCLUSTER-348 > URL: https://issues.jboss.org/browse/MODCLUSTER-348 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Environment: Windows Server 2008 > JBoss EAP 5.1.0 > EWS 1.0.1 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Attachments: chunked.log > > > DefaultMCMPHandler send MCMP requests to mod_manager with HTTP version 1.1, but it can't understand chunked-encoded responses. Chunked encoding is mandatory in HTTP 1.1 (RFC2616 3.6.1). > With lots of nodes, contexts and aliases, the INFO command can return a chunked-encoded response. Then, every STATUS command will fail with a NumberFormatException (cf log). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues July 2013