April 2011 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] Created: (MODCLUSTER-220) Extra REMOVE-APP event after failover

by Radoslav Husar (JIRA)

Extra REMOVE-APP event after failover ------------------------------------- Key: MODCLUSTER-220 URL: https://issues.jboss.org/browse/MODCLUSTER-220 Project: mod_cluster Issue Type: Enhancement Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Trivial Trivial thing: I think there is an extra REMOVE-APP event happening after fail-over. The test scenario is simple - start a node with 6 context, kill the node and reconnect. The apps are unchanged but 5 are remembered as were and one is removed and added back? Since they happen at the same time it looks like it happens uselessly and can cause race condition. {code} 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "INFO / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "STATUS / HTTP/1.0" 200 58 "-" "ClusterListener/1.0" ... 127.0.0.1 - - [04/Apr/2011:19:19:03 +0200] "GET /SessionTest/SessionTestServlet? HTTP/1.1" 200 1 "-" "Jakarta Commons-HttpClient/3.1" ... 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "INFO / HTTP/1.0" 200 575 "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "REMOVE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0" 127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "STATUS / HTTP/1.0" 200 58 "-" "ClusterListener/1.0" {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
21
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-199) Segmentation fault in Apache worker when using different balancernames and Aliases.

by Geert Pante (JIRA)

Segmentation fault in Apache worker when using different balancernames and Aliases. ----------------------------------------------------------------------------------- Key: MODCLUSTER-199 URL: https://jira.jboss.org/browse/MODCLUSTER-199 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: RedHat EL 5.5 x86_64, Apache 2.2.3, mod_cluster-1.1.0.Final-linux2-x64 Reporter: Geert Pante Assignee: Jean-Frederic Clere Hi all, We did a test setup with 2 apache servers and 2 backend JBoss servers. One JBoss Server has 2 applications deployed on one alias, and the other one has one application deployed as ROOT application context. In the jbossweb server.xml we set Aliases, and this worked most of the time, with applications http://alias1/app1, http://alias1/app2 and http://alias2/ all proxied nicely through both apache servers. The names alias1 and alias2 were mapped to a virtual IP that could be switched dynamically between the apache servers. However, we did have some problems that after a restart of one of the apache server, it would get 'All workers are in error state' for one of the applications, and it would no longer send ajp ping requests. The JBoss server continues to send STATUS messages happily. In mod_cluster-manager all seems well, too. Initially we used a default ManagerBalancerName in the Apache config, so both were using the same balancer. As a test we tried to remove the ManagerBalancerName in the apache config, and set a balancername in the mod_cluster-beans.xml. In mod_cluster-manager we saw the different balancers now, but again, on one of the apache servers, the proxying does not work, this time with a segmentation fault. See attached coredump =============================================== Core was generated by `/usr/sbin/httpd'. Program terminated with signal 11, Segmentation fault. (gdb) thread apply all bt full Thread 2 (Thread 31682): #0 0x00002b81583146f7 in kill () from /lib64/libc.so.6 No symbol table info available. #1 <signal handler called> No symbol table info available. #2 0x00002b815835d7c0 in strlen () from /lib64/libc.so.6 No symbol table info available. #3 0x00002b8157ca840e in ?? () from /usr/lib64/libapr-1.so.0 No symbol table info available. #4 0x7069626d00000000 in ?? () No symbol table info available. #5 0x00002b815f9755c8 in ?? () No symbol table info available. #6 0x00002b815669e230 in ?? () No symbol table info available. #7 0x00002b81566a1e08 in ?? () No symbol table info available. #8 0x00002b815f973f90 in ?? () No symbol table info available. #9 0x00002b815f32365f in cluster_get_sessionid (r=0x2b815f973f18, stickyval=0x1 <Address 0x1 out of bounds>, uri=0x2b815f9755c8 "/", sticky_used=0x7) at mod_proxy_cluster.c:1032 sticky = <value optimized out> sticky_path = <value optimized out> route = <value optimized out> #10 0x00002b815f324e92 in get_route_balancer (r=0x2b815f973f90, conf=0x2b815669d1a8) at mod_proxy_cluster.c:1788 balancer = 0x2b81566a1e08 route = <value optimized out> sessionid = <value optimized out> sticky_used = <value optimized out> i = 1 #11 0x00002b815f3251d5 in proxy_cluster_trans (r=0x1) at mod_proxy_cluster.c:1938 balancer = 0x2b815f973f90 "\030?\227_\201+" sconf = 0x2b815f9755c8 conf = 0x1 #12 0x00002b81563e4ba2 in ap_run_translate_name () No symbol table info available. #13 0x00002b81563e5e62 in ap_process_request_internal () No symbol table info available. #14 0x00002b81563f7968 in ap_should_client_block () No symbol table info available. #15 0x00002b815f963870 in ?? () No symbol table info available. #16 0x00002b815f973f90 in ?? () No symbol table info available. #17 0x00002b815f963870 in ?? () No symbol table info available. #18 0x0000000000000000 in ?? () No symbol table info available. Thread 1 (Thread 31683): #0 0x00002b81583b0fc2 in select () from /lib64/libc.so.6 No symbol table info available. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-183) NPE when overriding default load metric in ModClusterListener

by Paul Ferraro (JIRA)

NPE when overriding default load metric in ModClusterListener ------------------------------------------------------------- Key: MODCLUSTER-183 URL: https://jira.jboss.org/browse/MODCLUSTER-183 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.CR3 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.1.1.Final Tomcat/JBW's IntrospectionUtils doesn't handle properties of type Class. Consequently, if you try to override the loadMetricClass, you end up with a NullPointerException during startup, since the property value is read as a null. This property needs to be a String, rather than a Class. -- 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

12 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-232) Unable to override load properties when running in Tomcat 6

by Radoslav Husar (JIRA)

Unable to override load properties when running in Tomcat 6 ----------------------------------------------------------- Key: MODCLUSTER-232 URL: https://issues.jboss.org/browse/MODCLUSTER-232 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.10 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Blocker As described in http://docs.jboss.org/mod_cluster/1.0.0/html/javaproperties.html#d0e1716 Overriding a property like this {code} <Listener className="org.jboss.modcluster.ModClusterListener" loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" loadMetricCapacity="1" /> {code} even to the default throws exception {code} Apr 19, 2011 4:13:26 PM org.apache.tomcat.util.IntrospectionUtils setProperty WARNING: IAE org.jboss.modcluster.ModClusterListener@739e8329 loadMetricCapacity 5 java.lang.IllegalArgumentException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tomcat.util.IntrospectionUtils.setProperty(IntrospectionUtils.java:334) at org.apache.tomcat.util.IntrospectionUtils.setProperty(IntrospectionUtils.java:262) at org.apache.tomcat.util.digester.SetPropertiesRule.begin(SetPropertiesRule.java:208) at org.apache.tomcat.util.digester.Rule.begin(Rule.java:153) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1356) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1343) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1642) at org.apache.catalina.startup.Catalina.load(Catalina.java:524) at org.apache.catalina.startup.Catalina.load(Catalina.java:562) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-217) request hang with a node is stop in EC2

by Jean-Frederic Clere (JIRA)

request hang with a node is stop in EC2 --------------------------------------- Key: MODCLUSTER-217 URL: https://issues.jboss.org/browse/MODCLUSTER-217 Project: mod_cluster Issue Type: Bug Environment: EC2 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.0.10, 1.1.2.Final Once stopping the EC2 the socket is closed so the cping doesn't wait for ping but connectiontimeout which default to nodeTimeout and/or server timeout. That affects only the first request (per process) once the node has been cleaned. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-233) Documentation: wrong default loadMetricClass

by Radoslav Husar (JIRA)

Documentation: wrong default loadMetricClass -------------------------------------------- Key: MODCLUSTER-233 URL: https://issues.jboss.org/browse/MODCLUSTER-233 Project: mod_cluster Issue Type: Bug Reporter: Radoslav Husar Assignee: Jean-Frederic Clere As found by Michal Babacek: http://docs.jboss.org/mod_cluster/1.0.0/html/javaproperties.html Attribute loadMetricClass default: org.jboss.load.metric.impl.BusyConnectorsLoadMetric correct class: org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-184) Redeployment of application in Tomcat fails

by Ruslan Gainutdinov (JIRA)

Redeployment of application in Tomcat fails ------------------------------------------- Key: MODCLUSTER-184 URL: https://jira.jboss.org/browse/MODCLUSTER-184 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: Windows 7 x64, Java 1.6.0_18-b07 32bit, Tomcat 6.0.29 + APR 1.1.20 + load-demo.war manually unpacked into webapps/ folder. Reporter: Ruslan Gainutdinov Assignee: Jean-Frederic Clere Both methods of redeployment cause this error, either by pressing reload link in Tomcat manager webapp and by touching web.xml in load-demo webapplication. Log excerpt: 31.08.2010 10:30:41 org.apache.catalina.core.StandardContext reload INFO: Reloading this Context has started 31.08.2010 10:30:41 org.jboss.modcluster.ModClusterService DEBUG: Stop context [/load-demo] in host [localhost] 31.08.2010 10:30:41 org.jboss.modcluster.ModClusterService DEBUG: Start context [/load-demo] in host [localhost] 31.08.2010 10:30:41 org.apache.catalina.core.StandardPipeline registerValve INFO: Can't register valve org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve[/load-demo] java.lang.NoClassDefFoundError: org/jboss/servlet/http/HttpEvent at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.privateGetPublicMethods(Class.java:2547) at java.lang.Class.getMethods(Class.java:1410) at org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource.createManagedBean(MbeansDescriptorsIntrospectionSource.java:304) at org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource.execute(MbeansDescriptorsIntrospectionSource.java:84) at org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource.loadDescriptors(MbeansDescriptorsIntrospectionSource.java:77) at org.apache.tomcat.util.modeler.Registry.load(Registry.java:754) at org.apache.tomcat.util.modeler.Registry.loadDescriptors(Registry.java:866) at org.apache.tomcat.util.modeler.Registry.findManagedBean(Registry.java:651) at org.apache.tomcat.util.modeler.Registry.findManagedBean(Registry.java:963) at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:794) at org.apache.catalina.core.StandardPipeline.registerValve(StandardPipeline.java:302) at org.apache.catalina.core.StandardPipeline.addValve(StandardPipeline.java:448) at org.jboss.modcluster.catalina.CatalinaContext.addRequestListener(CatalinaContext.java:114) at org.jboss.modcluster.ModClusterService.start(ModClusterService.java:385) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:257) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4540) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:3391) at org.apache.catalina.manager.ManagerServlet.reload(ManagerServlet.java:943) at org.apache.catalina.manager.HTMLManagerServlet.reload(HTMLManagerServlet.java:556) at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:121) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:861) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1584) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: org.jboss.servlet.http.HttpEvent at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 38 more As I can see, it is caused by wrong method signature in class org.jboss.modcluster.catalina.CatalinaContext.RequestListenerValve public void event(Request request, Response response, HttpEvent event) throws IOException, ServletException -- 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

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-234) AverageSystemLoadMetric broken on Tomcat 6

by Radoslav Husar (JIRA)

AverageSystemLoadMetric broken on Tomcat 6 ------------------------------------------ Key: MODCLUSTER-234 URL: https://issues.jboss.org/browse/MODCLUSTER-234 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.10 Environment: Windows 2008, Tomcat 6 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Priority: Blocker Attachments: Screenshot-rdesktop - vmg14.mw.lab.eng.bos.redhat.com.png If the AverageSystemLoadMetric is specified {code} <Listener className="org.jboss.modcluster.ModClusterListener" loadMetricClass="org.jboss.modcluster.load.metric.impl.AverageSystemLoadMetric" /> {code} in Tomcat 6 that is supposed to Return CPU load - it alawys returns 100 all the time. See screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
7
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-226) Worker in error state after a request timeout

by Jean-Frederic Clere (JIRA)

Worker in error state after a request timeout --------------------------------------------- Key: MODCLUSTER-226 URL: https://issues.jboss.org/browse/MODCLUSTER-226 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.1.Final, 1.0.9 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere An application timeout mark a worker in ERROR, it might be nice to have a better control on that. In fact the modification would be mostly in Apache httpd mod_proxy code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-223) mod_cluster should issue a warning when Maxcontext is reached and no more context will be taken

by Baptiste MATHUS (JIRA)

mod_cluster should issue a warning when Maxcontext is reached and no more context will be taken ----------------------------------------------------------------------------------------------- Key: MODCLUSTER-223 URL: https://issues.jboss.org/browse/MODCLUSTER-223 Project: mod_cluster Issue Type: Enhancement Reporter: Baptiste MATHUS Assignee: Jean-Frederic Clere As a followup to MODCLUSTER-221, I think it would greatly help that httpd issues a warning when the maximum number of configured contexts is reached. Thanks a lot! PS: maybe this would be even better to also add informations about Max* values when using "AllowDisplay on" parameter. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2011