August 2014 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-317) windows mod_ssl.so broken

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-317?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-317. ------------------------------------- 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 > windows mod_ssl.so broken > ------------------------- > > Key: MODCLUSTER-317 > URL: https://issues.jboss.org/browse/MODCLUSTER-317 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.2.0.Final > Environment: win 32 / 64 > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.2.Final > > > Cannot load mod_ssl.so (Syntax error) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-283) Refactor ModClusterConfig to allow complex types

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-283?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-283. ------------------------------------- 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 > Refactor ModClusterConfig to allow complex types > ------------------------------------------------ > > Key: MODCLUSTER-283 > URL: https://issues.jboss.org/browse/MODCLUSTER-283 > Project: mod_cluster > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 1.2.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.2.1.Beta2 > > > mod_cluster's configuration interfaces were originally designed to accept simple configuration property values. With AS7, complex property types (e.g. InetAddress, Collection<InetSocketAddress>, Set<String>) are easier to define - and the old methods are now cumbersome. We should keep the old mutator methods (for backwards compatibility), but alter the accessor methods to accept more complex types. > e.g. > Collection<InetSocketAddress> MCMPConfiguration.getProxies(); > void ModClusterConfig.setProxies(Collection<InetSocketAddress>); > void ModClusterConfig.setProxyList(String proxyList); > InetAddress AdvertiseConfiguration.getAdvertiseGroupAddress(); > void ModClusterConfig.setProxies(Collection<InetSocketAddress>); > void ModClusterConfig.setProxyList(String proxyList); > etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-212) UseAlias broken

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-212?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-212. ------------------------------------- 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 > UseAlias broken > --------------- > > Key: MODCLUSTER-212 > URL: https://issues.jboss.org/browse/MODCLUSTER-212 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.5, 1.0.6, 1.0.8 > Environment: Windows Server 2008 x86 > Reporter: Gregory Lardiere > Assignee: Jean-Frederic Clere > Fix For: 1.0.9, 1.1.2.Final > > > Setting "UseAlias 1" in apache conf file doesn't work anymore since 1.0.5. It worked fine in 1.0.3 and 1.0.4. > Workers are correct in mod_cluster-manager. > The URLs behind a webapp context root return with a 404 error code. > With the UseAlias directive commented out, the problem doesn't happen. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-83) Add stop() methods to ModClusterServiceMBean

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-83?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-83. ------------------------------------ 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 stop() methods to ModClusterServiceMBean > -------------------------------------------- > > Key: MODCLUSTER-83 > URL: https://issues.jboss.org/browse/MODCLUSTER-83 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.GA > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.1.0.Beta1 > > > stop() : stop all apps on node > stop(String hostName, String contextPath) : stop single app > 1. Send disable request to proxy > 2. Wait for sessions to drain > 3. Send stop request to proxy -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-312) port JBPAPP-8956 to 1.2.x

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-312?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-312. ------------------------------------- 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 > port JBPAPP-8956 to 1.2.x > ------------------------- > > Key: MODCLUSTER-312 > URL: https://issues.jboss.org/browse/MODCLUSTER-312 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.2.1.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.2.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-191) JBoss Enterprise Application Platform * JBPAPP-5315 mod_cluster: proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-191?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-191. ------------------------------------- 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 > JBoss Enterprise Application Platform * JBPAPP-5315 mod_cluster: proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed > -------------------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-191 > URL: https://issues.jboss.org/browse/MODCLUSTER-191 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > > The problem is the following: > +++ > [Wed Oct 27 11:33:30 2010] [error] ajp_cping_cpong: apr_socket_recv failed > [Wed Oct 27 11:33:30 2010] [debug] mod_proxy_cluster.c(1213): ajp_cping_cpong: Done > [Wed Oct 27 11:33:30 2010] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (127.0.0.1) > +++ > and later: > +++ > [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS > [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4) > [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data > [Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 > [Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09 > [Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(543): proxy: Processing of request failed backend: 1, output: 0 > [Wed Oct 27 11:33:55 2010] [error] proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed > +++ > And the node is marked broken for a while, until: > +++ > Wed Oct 27 11:35:00 2010] [debug] proxy_util.c(1955): proxy: ajp: worker for (127.0.0.1) has been marked for retry > +++ > The STATUS should be able to restore the node and may be the answer 09 should not be taken as broken node error: it is just a broken socket error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-133) STATUS should retry the worker even if there was an error before.

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-133?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-133. ------------------------------------- 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 > STATUS should retry the worker even if there was an error before. > ----------------------------------------------------------------- > > Key: MODCLUSTER-133 > URL: https://issues.jboss.org/browse/MODCLUSTER-133 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.6 > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.8, 1.1.0.CR1 > > > Once an error occurs a STATUS should retry but the moment we have: > +++ > [Thu Feb 25 16:49:24 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09 > [Thu Feb 25 16:49:24 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09 > [Thu Feb 25 16:49:24 2010] [debug] mod_proxy_ajp.c(540): proxy: Processing of request failed backend: 1, output: 0 > [Thu Feb 25 16:49:24 2010] [error] proxy: dialog to 192.168.100.150:8009 (192.168.100.150) failed > [Thu Feb 25 16:49:24 2010] [debug] proxy_util.c(2017): proxy: AJP: has released connection for (192.168.100.150) > [Thu Feb 25 16:49:24 2010] [debug] mod_proxy_cluster.c(1118): proxy: byrequests balancer FAILED > [Thu Feb 25 16:49:24 2010] [error] proxy: CLUSTER: (balancer://mycluster). All workers are in error state > [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/) > [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1929): manager_handler STATUS (/) processing: "JVMRoute=node3&Load=78" > [Thu Feb 25 16:49:26 2010] [debug] proxy_util.c(1937): proxy: ajp: retrying the worker for (192.168.100.150) > [Thu Feb 25 16:49:26 2010] [error] proxy: ajp: disabled connection for (192.168.100.150) > [Thu Feb 25 16:49:26 2010] [debug] mod_proxy_cluster.c(1333): proxy_cluster_isup: pingpong failed > [Thu Feb 25 16:49:26 2010] [debug] mod_manager.c(1970): manager_handler STATUS OK > [Thu Feb 25 16:49:36 2010] [debug] mod_manager.c(1416): manager_trans STATUS (/) > [Thu Feb 25 16:49:36 2010] [debug] mod_manager.c(1929): manager_handler STATUS (/) processing: "JVMRoute=node3&Load=77" > [Thu Feb 25 16:49:36 2010] [debug] proxy_util.c(1937): proxy: ajp: retrying the worker for (192.168.100.150) > [Thu Feb 25 16:49:36 2010] [error] proxy: ajp: disabled connection for (192.168.100.150) > +++ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-73) Advertise worker thread can throw NullPointerException on AdvertiseListener.destroy()

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-73?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-73. ------------------------------------ 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 > Advertise worker thread can throw NullPointerException on AdvertiseListener.destroy() > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-73 > URL: https://issues.jboss.org/browse/MODCLUSTER-73 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Minor > Fix For: 1.0.0.CR2 > > > AdvertiseListenerImpl can throw a NullPointerException if AdvertiseListener.destroy() completes before the worker thread is done with the socket. > +++ > [java] Test DONE > [java] Exception in thread "Thread-30" java.lang.NullPointerException > [java] at > org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl$AdvertiseListenerWorker.run(AdvertiseListenerImpl.java:422) > +++ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-268) emptySessionPathed JSESSIONID.jvmRoute cookies results in requests being improperly sent to mod_cluster workers

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-268?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-268. ------------------------------------- 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 > emptySessionPathed JSESSIONID.jvmRoute cookies results in requests being improperly sent to mod_cluster workers > --------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-268 > URL: https://issues.jboss.org/browse/MODCLUSTER-268 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP01 > Environment: JBoss EAP 5.1.1 > EWS 1.0.2 > MOD_CLUSTER 1.0.10.GA_CP01 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: MOD_CLUSTER_1_0_10_GA_CP03 > > > Empty session paths can result in requests being sent to mod_cluster workers that shouldn't be. For example, if a request for apache-served static content has an applicable JSESSIONID (either because the path matches the context or its an empty path and matches everything) with a route valve appended to it, then the static content request is directed to the mod_cluster balancer, resulting in 503s and "All workers are in error state". > So it looks like the presence of a jsessionid.jvmroute cookie causes apache/mod_cluster to improperly route the request even if its a context not handled by any mod_cluster workers. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-177) Deprecate use of term "domain"

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-177?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-177. ------------------------------------- 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 > Deprecate use of term "domain" > ------------------------------ > > Key: MODCLUSTER-177 > URL: https://issues.jboss.org/browse/MODCLUSTER-177 > Project: mod_cluster > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.CR3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.1.0.Final > > > In AS7, the term "domain" will be used to refer to a unit of management. To preempt any future confusion, we should deprecate this term and replace it with something else - TBD. Affects both code, configuration, and docs. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 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