mod_cluster-issues@lists.jboss.org

1 participants
15 discussions

[JBoss JIRA] Created: (MODCLUSTER-102) random 404 errors

by Gabor Veres (JIRA)

random 404 errors ----------------- Key: MODCLUSTER-102 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-102 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: Linux 2.6.28-15-generic #49-Ubuntu SMP, apache 2.2, JBoss EAP 4.3 Reporter: Gabor Veres Assignee: Jean-Frederic Clere Attachments: other_vhosts_access.log Stress testing with the mod_cluster provided demo client, or any other web stressing tool shows random 404 errors when accessing resources meant to be provided by the backend JBoss Application Servers. Please see the forum reference for some more details. -- 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

14 years, 11 months

2
24
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-113) load-demo.war specifies non-existent servlet in web.xml

by Brian Stansberry (JIRA)

load-demo.war specifies non-existent servlet in web.xml ------------------------------------------------------- Key: MODCLUSTER-113 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-113 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA, 1.0.1.GA, 1.0.0.GA, 1.1.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 1.1.0.CR1 The org.jboss.modcluster.demo.servlet.ThreadCountLoadServlet was removed between 1.0.0.CR2 and 1.0.0.GA, but it's still specified in the load-demo.war's web.xml, resulting in deployment errors. It's also mentioned on http://www.jboss.org/mod_cluster/demo.html -- 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

14 years, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-117) ERROR [DefaultMCMPHandler] Error [null: null: {4}] sending command INFO to proxy 152.168.15.130:7777, configuration will be reset error when using MOD_CLUSTER 1.0.2 GA with JBOSS 5.0.0

by Rajah Harris (JIRA)

ERROR [DefaultMCMPHandler] Error [null: null: {4}] sending command INFO to proxy 152.168.15.130:7777, configuration will be reset error when using MOD_CLUSTER 1.0.2 GA with JBOSS 5.0.0 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: MODCLUSTER-117 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-117 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: Windows, JBOSS 5.0.0 Reporter: Rajah Harris Assignee: Jean-Frederic Clere Priority: Critical Fix For: 1.0.2.GA Hello, i'm testing mod_cluster 1.0.2 GA with JBoss 5.0.0 GA in a windows environment for testing purposes and i'm recieving this error: 16:24:21,906 ERROR [DefaultMCMPHandler] Error [null: null: {4}] sending command INFO to proxy 152.168.15.130:7777, configuration will be reset error I saw a listing in JIRA that ya'll set up for this, https://jira.jboss.org/jira/browse/MODCLUSTER-61, saying that it only happens in a windows environment but that was in an ealier version of Mod_Cluster. I'm looking to see what i can do to avoid that error. Because it is effecting my testing as it seems to recognize the node in the manager, but the jboss default site/location isn't proxied correctly through the mod_cluster. Oh yeah, i and i'm using the AJP connector as well. The Mod_cluster corresponding error message in the log is "[Wed Dec 23 13:32:57 2009] [error] [client 152.168.15.130] client denied by server configuration: C:/ " Any input would be much appreciated, thank you. -- 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

14 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-116) Microcontainer does not always choose the right constructor when creating ModClusterService

by Paul Ferraro (JIRA)

Microcontainer does not always choose the right constructor when creating ModClusterService ------------------------------------------------------------------------------------------- Key: MODCLUSTER-116 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-116 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.1.0.CR1 A user encountered the following error when attempting to start EAP 5.0.0 w/mod_cluster 1.1.0.Beta1: 09:25:15,078 ERROR [AbstractKernelController] Error installing to Instantiated: name=ModClusterService state=Described mode=On Demand requiredState=Installed java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.modcluster.config.ModClusterConfig, org.jboss.modcluster.load.LoadBalanceFactorProviderFactory] actual=[org.jboss.modcluster.config.ha.HAModClusterConfig, org.jboss.modcluster.load.impl.DynamicLoadBalanceFactorProvider] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) The microcontainer is trying to instantiate ModClusterService using the wrong constructor. The mod_cluster-jboss-beans.xml should be updated to explicitly define the parameter types to remove this ambiguity. -- 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

15 years

1
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-110) Split ModClusterServiceMBean.ping(String) into 3 methods

by Paul Ferraro (JIRA)

Split ModClusterServiceMBean.ping(String) into 3 methods -------------------------------------------------------- Key: MODCLUSTER-110 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-110 Project: mod_cluster Issue Type: Feature Request Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Fix For: 1.1.0.CR1 Currently the ModClusterServiceMBean.ping(String) method does 3 things: 1. If parameter is null, send a PING command that determines the accessibility/health of each proxy. 2. If parameter is not a url, interpret the parameter as a jvm route and send a PING command that determines the accessibility of the node, configured with the specified jvm route, from each proxy. 3. If parameter is as a url, interpret the parameter as a url and send a PING command that determines the accessibility of the node (which may or may not be configured in the proxy already) containing a connector matching the protocol, host, and port of the url, from each proxy . Rather than 1 multi-purpose function - this method should be split in to 3, corresponding to the 3 functions identified above: Map<InetSocketAddress, String> ping(); Map<InetSocketAddress, String> ping(String jvmRoute); Map<InetSocketAddress, String> ping(String protocol, String host, int port); or perhaps: Map<InetSocketAddress, String> pingProxies(); Map<InetSocketAddress, String> pingNode(String jvmRoute); Map<InetSocketAddress, String> pingConector(String url); -- 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

15 years

2
3
0 / 0

← Newer
1
2
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues December 2009