August 2014 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-87) admin-console should be in the excludedContexts

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-87?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-87. ------------------------------------ Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > admin-console should be in the excludedContexts > ----------------------------------------------- > > Key: MODCLUSTER-87 > URL: https://issues.jboss.org/browse/MODCLUSTER-87 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Paul Ferraro > Priority: Minor > Fix For: 1.0.2.GA, 1.1.0.Beta1 > > > mod_cluster lists /admin-console by default in the deployed application... But it shouldn't. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-278) CatalinaConnector.setAddress not working with Tomcat <= 6.0.14

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-278?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-278. ------------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > CatalinaConnector.setAddress not working with Tomcat <= 6.0.14 > -------------------------------------------------------------- > > Key: MODCLUSTER-278 > URL: https://issues.jboss.org/browse/MODCLUSTER-278 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.3.Final > Environment: Tomcat 6.0.13 + jdk 1.6 > Reporter: Stefano Nichele > Assignee: Jean-Frederic Clere > > If in the server.xml file the "address" property is not specified, mod-cluster calls > IntrospectionUtils.setProperty(this.connector.getProtocolHandler(), "address", address.getHostAddress()); > in order to set the address automatically. > This calls doesn't work with tomcat <= 6.0.14 (CatalinaConnector.setAddress throws a NoSuchMethodError) since the signature of IntrospectionUtils.setProperty has been changed in tomcat 6.0.15. > As a fix, I would like to suggest this small changes in CatalinaConnector.setAddress: > > try { > IntrospectionUtils.setProperty(this.connector.getProtocolHandler(), "address", address.getHostAddress()); > } catch (NoSuchMethodError err) { > // this works on Tomcat <= 6.0.14 > this.connector.getProtocolHandler().setAttribute("address", address.getHostAddress()); > } > instead of just: > > IntrospectionUtils.setProperty(this.connector.getProtocolHandler(), "address", address.getHostAddress()); -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-266) warning while compiling on some lab boxes

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-266?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-266. ------------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > warning while compiling on some lab boxes > ----------------------------------------- > > Key: MODCLUSTER-266 > URL: https://issues.jboss.org/browse/MODCLUSTER-266 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.3.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.2.0.Beta4 > > > size_t != int on any platform (on 64-bit its usually 64) > However think you are not using +2G sizes. However it might > break on negative values due to unsigned int64 -> int32 conversion. > .\mod_proxy_cluster.c(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data > .\mod_proxy_cluster.c(1026) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data > .\mod_proxy_cluster.c(1020) : warning C4101: 'name' : unreferenced local variable > .\mod_proxy_cluster.c(1092) : warning C4101: 'ret' : unreferenced local variable > .\mod_proxy_cluster.c(1225) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data > .\mod_proxy_cluster.c(1226) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data > .\mod_proxy_cluster.c(1910) : warning C4244: 'return' : conversion from '__int64' to 'int', possible loss of data > .\mod_proxy_cluster.c(2040) : warning C4267: 'function' : conversion from 'size_t' to 'int', possible loss of data -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-7) Management interface for ModClusterService

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-7?page=com.atlassian.jira.plug... ] Michal Babacek closed MODCLUSTER-7. ----------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > Management interface for ModClusterService > ------------------------------------------ > > Key: MODCLUSTER-7 > URL: https://issues.jboss.org/browse/MODCLUSTER-7 > Project: mod_cluster > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering, Web (Tomcat) service > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Define the management attributes and operations. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-100) load balancing logic doesn't allow manual demo of load-balancing

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-100?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-100. ------------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > load balancing logic doesn't allow manual demo of load-balancing > ---------------------------------------------------------------- > > Key: MODCLUSTER-100 > URL: https://issues.jboss.org/browse/MODCLUSTER-100 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.1.GA > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.2.GA, 1.1.0.Beta1 > > > the load-balancing logic counts the requests during a while and uses that counter to balance the requests between the nodes. > the while is 1 second fixed.... Should be a parameter and probably the default value should be more than one second. > The actual ormula is: > status = lbstatus + (elected - oldelected) * 1000)/bfactor; > lbfactor is received for the node via STATUS. > lbstatus is recalculated every 1 second (that will be a parameter) like status. > elected is the number of time the worker was elected. > oldelected is elected last time the lbstatus was recalculated. > The node with the lowest status is selected. > If you have very few sessions (like a demo by hands) lbstatus is 0 on all the nodes and only the first nodes are going to be selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-76) Add httpd.conf property to specify bind address for mod_advertise

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-76?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-76. ------------------------------------ Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > Add httpd.conf property to specify bind address for mod_advertise > ----------------------------------------------------------------- > > Key: MODCLUSTER-76 > URL: https://issues.jboss.org/browse/MODCLUSTER-76 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.GA > > > Something like: > AdvertiseBindAddress 127.0.0.1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-228) Tomcat6 throws java.lang.NoSuchMethodError instead a localised error messages.

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-228?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-228. ------------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > Tomcat6 throws java.lang.NoSuchMethodError instead a localised error messages. > ------------------------------------------------------------------------------ > > Key: MODCLUSTER-228 > URL: https://issues.jboss.org/browse/MODCLUSTER-228 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.9 > Environment: Tomcat 6.0.x > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.10 > > > mod_cluster is compiled with jbossweb-2.1.x where we have in org/apache/tomcat/util/res/StringManager.java. > public String getString(String key, Object arg1, Object arg2, Object arg3) > but Tomcat has: > public String getString(final String key, final Object... args) > So java.io.FileNotFoundException :-( -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-25) Setup java build in Hudson

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-25?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-25. ------------------------------------ Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > Setup java build in Hudson > -------------------------- > > Key: MODCLUSTER-25 > URL: https://issues.jboss.org/browse/MODCLUSTER-25 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-271) Error 404 after successful cluster switch

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-271?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-271. ------------------------------------- Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > Error 404 after successful cluster switch > ----------------------------------------- > > Key: MODCLUSTER-271 > URL: https://issues.jboss.org/browse/MODCLUSTER-271 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.3.Final > Reporter: Erhard Siegl > Assignee: Jean-Frederic Clere > > mod_cluster with two JBoss 4 as backend. A client continuousely hits the server. > When I shutdown the JBoss with the active session, the second takes over successfully. But then sometimes I get a 404 for a single hit. Parts from the logfile (with debug): > [Thu Dec 29 19:16:07 2011] [debug] mod_proxy_ajp.c(644): proxy: AJP: serving URL ajp://192.168.40.129:8109/demo/ > ... > [Thu Dec 29 19:16:07 2011] [debug] ajp_header.c(516): ajp_unmarshal_response: status = 200 > ... Shutdown of first node > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(2296): manager_handler DISABLE-APP (/) processing: "JVMRoute=cluster1&Alias=localhost&Context=%2Fdemo" > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(2339): manager_handler DISABLE-APP OK > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(1653): manager_trans STOP-APP (/) > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(2296): manager_handler STOP-APP (/) processing: "JVMRoute=cluster1&Alias=localhost&Context=%2Fdemo" > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(2339): manager_handler STOP-APP OK > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(1653): manager_trans REMOVE-APP (/) > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(2296): manager_handler REMOVE-APP (/) processing: "JVMRoute=cluster1&Alias=localhost&Context=%2Fdemo" > [Thu Dec 29 19:16:07 2011] [debug] mod_manager.c(2339): manager_handler REMOVE-APP OK > ... Successfully removed route > [Thu Dec 29 19:16:08 2011] [debug] mod_proxy_ajp.c(644): proxy: AJP: serving URL ajp://192.168.123.231:8209/demo/ > ... > [Thu Dec 29 19:16:08 2011] [debug] ajp_header.c(516): ajp_unmarshal_response: status = 200 > ... But then it uses ajp://192.168.40.129:8109/demo/ again and fails with 404 > [Thu Dec 29 19:16:09 2011] [debug] proxy_util.c(1937): proxy: BALANCER: retrying the worker for (192.168.40.129) > [Thu Dec 29 19:16:09 2011] [debug] proxy_util.c(1943): proxy: BALANCER: worker for (192.168.40.129) has been marked for retry > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy.c(993): Running scheme balancer handler (attempt 0) > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy_http.c(1930): proxy: HTTP: declining URL ajp://192.168.40.129:8109/demo/ > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy_scgi.c(508): [client 127.0.0.1] proxy: SCGI: declining URL ajp://192.168.40.129:8109/demo/ > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy_ajp.c(644): proxy: AJP: serving URL ajp://192.168.40.129:8109/demo/ > [Thu Dec 29 19:16:09 2011] [debug] proxy_util.c(1999): proxy: AJP: has acquired connection for (192.168.40.129) > [Thu Dec 29 19:16:09 2011] [debug] proxy_util.c(2055): proxy: connecting ajp://192.168.40.129:8109/demo/ to 192.168.40.129:8109 > [Thu Dec 29 19:16:09 2011] [debug] proxy_util.c(2153): proxy: connected /demo/ to 192.168.40.129:8109 > [Thu Dec 29 19:16:09 2011] [debug] ajp_utils.c(31): Into ajp_handle_cping_cpong > [Thu Dec 29 19:16:09 2011] [debug] ajp_utils.c(102): ajp_handle_cping_cpong: Done > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(224): Into ajp_marshal_into_msgb > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[0] [Accept-Encoding] = [identity] > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[1] [Host] = [devjava] > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[2] [Cookie] = [JSESSIONID=D6AcPj+99EObFqH+F9wjew**.cluster1] > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[3] [Connection] = [close] > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(290): ajp_marshal_into_msgb: Header[4] [User-agent] = [Mozilla/4.0 (compatible; MSIE 5.5; Windows NT)] > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(450): ajp_marshal_into_msgb: Done > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4) > [Thu Dec 29 19:16:09 2011] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 04 > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(697): ajp_parse_type: got 04 > [Thu Dec 29 19:16:09 2011] [debug] ajp_header.c(516): ajp_unmarshal_response: status = 404 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-46) httpd.conf in standard binary dist loads incompatible mod_proxy_balancer

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-46?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-46. ------------------------------------ Closing. Clean-up. At least one of the following applies: * the issue has been thoroughly tested as a part of one of the current releases or * it hasn't occurred in ~2 years or * it's utterly harmless > httpd.conf in standard binary dist loads incompatible mod_proxy_balancer > ------------------------------------------------------------------------ > > Key: MODCLUSTER-46 > URL: https://issues.jboss.org/browse/MODCLUSTER-46 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta3 > Reporter: Brian Stansberry > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.Beta4 > > > The httpd.conf that ships with the 1.0.0.Beta3 binary download includes this: > LoadModule proxy_balancer_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_balancer.so > which causes httpd to fail to start with this: > [Tue Feb 03 12:53:28 2009] [error] Module mod_proxy_balancer is loaded it must be removed in order for mod_proxy_cluster to function properly > Configuration Failed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2014