December 2010 - mod_cluster-issues

[JBoss JIRA] Created: (MODCLUSTER-105) Refactor mod_cluster to allow implementations for other application servers

by Paul Ferraro (JIRA)

Refactor mod_cluster to allow implementations for other application servers --------------------------------------------------------------------------- Key: MODCLUSTER-105 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-105 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.0.2.GA Reporter: Paul Ferraro Assignee: Paul Ferraro Split current jar into a -core.jar containing APIs, and isolate catalina implementation to a separate -catalina.jar. -- 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

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-112) Refactor project into modules for HA, catalina, core, etc.

by Paul Ferraro (JIRA)

Refactor project into modules for HA, catalina, core, etc. ---------------------------------------------------------- Key: MODCLUSTER-112 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-112 Project: mod_cluster Issue Type: Sub-task Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Restructure maven project to create separate module jars. mod-cluster-spi: ContainerEventHandler, Server, Engine, Connector, Host, Context mod-cluster-core: ModClusterService and dependencies mod-cluster-ha: HAModClusterService and dependencies mod-cluster-catalina: ModClusterListener, CatalinaEventHandlerAdapter and spi implementation -- 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

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx

by Paul Ferraro (JIRA)

Modify jbossweb metrics to use service provider spi, instead of jmx ------------------------------------------------------------------- Key: MODCLUSTER-151 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-151 Project: mod_cluster Issue Type: Feature Request Affects Versions: 1.1.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric, BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric, SendTrafficLoadMetric) use jmx to generate their load values. This is potentially fragile. Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context. This raises the issue of load value scope. Currently, load is scoped to a server. Really, this should be scoped to an engine. While server:engine is usually a 1:1 relationship, this is technically a 1:N relationship. Suggested API change: class LoadMetricSource<C extends LoadContext> { C createContext(Engine engine); } Where there exists: class EngineLoadMetricSource<EngineLoadContext> { public EngineLoadContext createContext(Engine engine) { return new EngineLoadContext(engine); } } class EngineLoadContext implements LoadContext { private final Engine engine; public EngineLoadContext(Engine engine) { this.engine = engine; } public Engine getEngine() { return this.engine; } public void close() { // Nothing to close } } The various jbossweb load metrics would use this source. -- 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

12 years, 4 months

6
6
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-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

12 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-197) Windows x86 Missing httpd.conf + other files in 1.1.0 distribution

by Greg Zoller (JIRA)

Windows x86 Missing httpd.conf + other files in 1.1.0 distribution ------------------------------------------------------------------ Key: MODCLUSTER-197 URL: https://jira.jboss.org/browse/MODCLUSTER-197 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Final Environment: Windows x86 Reporter: Greg Zoller Assignee: Jean-Frederic Clere According to the docs mod_cluster ships with a preconfigured httpd instance: just unpack and run. Unfortunately the Windows x86 version doesn't include all the conf files set up as the Linux distribution appears to have. These files need to be added or the documentation amended to reflect this. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-118) character ? in

by Dmitry Sanatin (JIRA)

character ? in --------------- Key: MODCLUSTER-118 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-118 Project: mod_cluster Issue Type: Bug Affects Versions: 1.1.0.Beta1 Environment: Windows 7 Ultimate, Apache 2.2.14 , JBoss web/Tomcat configuration Reporter: Dmitry Sanatin Assignee: Jean-Frederic Clere URI of http request is truncated up to '?' character at apache side. Cluster node receive wrong request. . If '?' is replaced by '%3f', it is passed to jboss "correctly". There is no such problem with 1.0.2 GA version. -- 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

13 years

2
8
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-90) Add information in httpd to find easly the mod_cluster version

by Jean-Frederic Clere (JIRA)

Add information in httpd to find easly the mod_cluster version -------------------------------------------------------------- Key: MODCLUSTER-90 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-90 Project: mod_cluster Issue Type: Feature Request Environment: httpd Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Priority: Minor Something like the header: Server: Apache/2.2.12-dev (Unix) mod_ssl/2.2.12-dev OpenSSL/0.9.8k-fips DAV/2 for example. -- 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

13 years

3
9
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-119) AdvertiseBindAddress does not default to the 23364 port

by Radoslav Husar (JIRA)

AdvertiseBindAddress does not default to the 23364 port ------------------------------------------------------- Key: MODCLUSTER-119 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-119 Project: mod_cluster Issue Type: Bug Affects Versions: 1.0.2.GA Environment: Fedora 11 Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Hello, it looks as though 1.0.2 GA does not pick the default value for AdvertiseBindAddress and listens on random port each time whereas the documentation claims it defaults to the same setup as the AS part default setup. The docs say: AdvertiseBindAddress IP:port: That is the address and port httpd is bind to send the multicast messages. This allow to specify an address on multi IP address boxes. Default: 0.0.0.0:23364 Here is the different starts/stops and ports, below the host config without ABA set. [rhusar@rhusar modcluster]$ netstat -lpn | grep http (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::8888 :::* LISTEN 19610/httpd udp 0 0 0.0.0.0:60958 0.0.0.0:* 19610/httpd [rhusar@rhusar modcluster]$ netstat -lpn | grep http (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::8888 :::* LISTEN 19648/httpd udp 0 0 0.0.0.0:34758 0.0.0.0:* 19648/httpd [rhusar@rhusar modcluster]$ netstat -lpn | grep http (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::8888 :::* LISTEN 19676/httpd udp 0 0 0.0.0.0:58988 0.0.0.0:* 19676/httpd <VirtualHost *:8888> KeepAliveTimeout 60 MaxKeepAliveRequests 0 ManagerBalancerName mycluster AdvertiseFrequency 5 # File a Jira - not in sync with docs # http://www.jboss.org/mod_cluster/native/config.html # AdvertiseBindAddress 0.0.0.0:23364 </VirtualHost> -- 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

13 years

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues December 2010