June 2011 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] Created: (MODCLUSTER-243) mod_cluster throws warnings at shutdown in AS7

by Jean-Frederic Clere (JIRA)

mod_cluster throws warnings at shutdown in AS7 ---------------------------------------------- Key: MODCLUSTER-243 URL: https://issues.jboss.org/browse/MODCLUSTER-243 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.2.Final Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor Fix For: 1.1.3.Final At shutdown you get an warning: +++ 21:37:37,537 WARN [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-1) Failed to interrupt socket reception: java.io.IOException: Invalid argument at java.net.PlainDatagramSocketImpl.send(Native Method) [:1.6.0_22] at java.net.DatagramSocket.send(DatagramSocket.java:629) [:1.6.0_22] at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.interruptDatagramReader(AdvertiseListenerImpl.java:240) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.stop(AdvertiseListenerImpl.java:262) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.destroy(AdvertiseListenerImpl.java:278) at org.jboss.modcluster.ModClusterService.shutdown(ModClusterService.java:214) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.destroy(CatalinaEventHandlerAdapter.java:374) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.stop(CatalinaEventHandlerAdapter.java:144) at org.jboss.as.modcluster.ModClusterService.stop(ModClusterService.java:236) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1819) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2302) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] +++ In fact that should be a debug... And the fix should go in mod_cluster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-219) AS7 schema requires properties.

by Jean-Frederic Clere (JIRA)

AS7 schema requires properties. ------------------------------- Key: MODCLUSTER-219 URL: https://issues.jboss.org/browse/MODCLUSTER-219 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.1.Final Reporter: Jean-Frederic Clere Assignee: Paul Ferraro Fix For: 1.1.2.Final In the xsd we have: +++ <xs:complexType name="common-load-metricType" abstract="true"> <xs:sequence> <xs:element name="property" type="tns:propertyType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="weight" type="xs:int"/> <xs:attribute name="capacity" type="xs:double"/> </xs:complexType> +++ So a getProperties() and a setProperties() should be added AbstractLoadMetric for example? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-209) mod_cluster_manager need better presentation

by Anders Welen (JIRA)

mod_cluster_manager need better presentation -------------------------------------------- Key: MODCLUSTER-209 URL: https://issues.jboss.org/browse/MODCLUSTER-209 Project: mod_cluster Issue Type: Enhancement Affects Versions: 1.1.1.Final Reporter: Anders Welen Assignee: Jean-Frederic Clere Priority: Minor The mod_cluster_manager "show INFO output" status page has the following problems: 1. "Transferred" misspelled 2. Context is missing the number of requests PS. Why not make it easier to parse? look at mod_jk that support both properties and XML DS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-242) requests routed to nodes where the context doesn't exist

by Samuel Mendenhall (JIRA)

requests routed to nodes where the context doesn't exist -------------------------------------------------------- Key: MODCLUSTER-242 URL: https://issues.jboss.org/browse/MODCLUSTER-242 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.10 Reporter: Samuel Mendenhall Assignee: Jean-Frederic Clere Fix For: 1.0.11 Env: 4 JBoss servers w/ mod_cluster sitting behind 2 Apache servers. The 2 Apache servers are proxying to the 4 JBoss servers. Those 4 JBoss servers are split into 2 separate clusters, each cluster serving different applications. For example, Cluster1 has AppA and AppB, but Cluster2 has AppC and Appd. When attempting to connect to any application through the Apache server, we randomly see 404 errors. Is this because Apache/mod_cluster is trying to route the request to all servers, instead of just the servers with the right web context enabled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[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-241) kill -HUP httpd process increase the open locks.

by Jean-Frederic Clere (JIRA)

kill -HUP httpd process increase the open locks. ------------------------------------------------ Key: MODCLUSTER-241 URL: https://issues.jboss.org/browse/MODCLUSTER-241 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.2.Final , 1.0.10 Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 1.1.3.Final start httpd and kill -HUP the process. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
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, 11 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, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-238) contexts and hosts for a broken node are not removed

by Jean-Frederic Clere (JIRA)

contexts and hosts for a broken node are not removed ---------------------------------------------------- Key: MODCLUSTER-238 URL: https://issues.jboss.org/browse/MODCLUSTER-238 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.2.Final , 1.0.10 Environment: any Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: MOD_CLUSTER_1_0_10_GA_CP01, 1.1.3.Final kill -9 a node and wait 5 minutes, then try info or restart the node and look in server.log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues June 2011