August 2014 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-106) Allow advertise listener to listen on a specific network interface

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-106?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-106. ------------------------------------- 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 > Allow advertise listener to listen on a specific network interface > ------------------------------------------------------------------ > > Key: MODCLUSTER-106 > URL: https://issues.jboss.org/browse/MODCLUSTER-106 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.GA > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.1.0.Beta1 > > > If null, listen on all interfaces (current behavior). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-94) getProxyInfo failed when there are too many nodes

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-94?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-94. ------------------------------------ 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 > getProxyInfo failed when there are too many nodes > ------------------------------------------------- > > Key: MODCLUSTER-94 > URL: https://issues.jboss.org/browse/MODCLUSTER-94 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.GA > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.2.GA, 1.1.0.Beta1 > > > When trying to test with 100 nodes it fails because getProxyInfo doesn't read correctly long message for httpd. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-253) ROOT in excludedContexts doesn't work

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-253?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-253. ------------------------------------- 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 > ROOT in excludedContexts doesn't work > ------------------------------------- > > Key: MODCLUSTER-253 > URL: https://issues.jboss.org/browse/MODCLUSTER-253 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP02, 1.1.3.Final > Environment: 5.1.x > Reporter: Jean-Frederic Clere > Assignee: Paul Ferraro > Fix For: MOD_CLUSTER_1_0_10_GA_CP03 > > > Just do: > <property name="excludedContexts">ROOT,admin-console,invoker,jbossws,jmx-console,juddi,web-console</property> > and see: > [Thu Sep 01 10:12:07 2011] [debug] mod_manager.c(2296): manager_handler ENABLE-APP (/) processing: "JVMRoute=4e6189af-0502-3305-8ff3-fad7fee8b516&Alias=localhost&Context=%2F" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-248) Missing Documentation For mod_cluster with JBoss AS5

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-248?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-248. ------------------------------------- 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 > Missing Documentation For mod_cluster with JBoss AS5 > ---------------------------------------------------- > > Key: MODCLUSTER-248 > URL: https://issues.jboss.org/browse/MODCLUSTER-248 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stefan Negrea > Assignee: Jean-Frederic Clere > Fix For: 1.2.0.Final > > > On the current mod_cluster website there is no documentation on installing mod_cluster on a JBoss AS5 server. The documentation says that mod_cluster is distributed with the server and implies there is no additional configuration required. However, it does not include details like adding Listeners to <Server> tag and configuring the JMX MBean and dependencies. > The documentation from the mod_cluster module delivered with the JBoss AS5 points to a website that is no longer valid (http://www.jboss.org/mod_cluster/java/config.html) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-53) Error state recording in ClusteredMCMPHandler can cause unnecessary reset requests

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-53?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-53. ------------------------------------ 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 state recording in ClusteredMCMPHandler can cause unnecessary reset requests > ---------------------------------------------------------------------------------- > > Key: MODCLUSTER-53 > URL: https://issues.jboss.org/browse/MODCLUSTER-53 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.0.0.Beta4 > > > Change List<Boolean> to a AtomicReference<ResetState>, where ResetState is: > enum ResetState { NONE, REQUIRED, PENDING } > Reset is necessary if state == ResetState.REQUIRED > Recording the initiation of a reset set the state to ResetState.PENDING > Recording the completion of a reset changes the state to NONE, only if the state is still ResetState.PENDING -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-182) mod_cluster logs "[error] [client <ip>] proxy: error processing body" when the client ends the connection prematurely

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-182?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-182. ------------------------------------- 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 > mod_cluster logs "[error] [client <ip>] proxy: error processing body" when the client ends the connection prematurely > --------------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-182 > URL: https://issues.jboss.org/browse/MODCLUSTER-182 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.3.GA > Reporter: Samuel Mendenhall > Assignee: Jean-Frederic Clere > > In mod_jk when the client closes the connection unexpedtedly the following error log messages are produced: > [Fri Jul 30 12:08:26 2010] [error] [client <ip>] proxy: error processing body > [Fri Jul 30 12:08:26 2010] [error] proxy: dialog to 192.168.0.1:8009 (192.168.0.1) failed > These messages should be logged as [warn] or [debug] not [error]. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-63) Undeploy an app or shut down server, clients with an existing session do not fail over.

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-63?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-63. ------------------------------------ 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 > Undeploy an app or shut down server, clients with an existing session do not fail over. > ---------------------------------------------------------------------------------------- > > Key: MODCLUSTER-63 > URL: https://issues.jboss.org/browse/MODCLUSTER-63 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.CR1 > > > Undeploy an app or shut down server, clients with an existing session do not fail over. Following from access_log shows the issue. Last 404 occurs a couple seconds after the REMOVE-APP, so doesn't seem to be a race. > > 192.168.2.3 - - [16/Mar/2009:16:07:48 +0100] "STOP-APP / HTTP/1.0" 200 - > > 127.0.0.1 - - [16/Mar/2009:16:07:48 +0100] "GET /load-demo/record HTTP/1.1" 503 1086 > > 127.0.0.1 - - [16/Mar/2009:16:07:48 +0100] "GET /load-demo/record HTTP/1.1" 503 1086 > > 127.0.0.1 - - [16/Mar/2009:16:07:48 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:48 +0100] "GET /load-demo/record HTTP/1.1" 503 1086 > > 127.0.0.1 - - [16/Mar/2009:16:07:48 +0100] "GET /load-demo/record HTTP/1.1" 503 1086 > > 127.0.0.1 - - [16/Mar/2009:16:07:48 +0100] "GET /load-demo/record HTTP/1.1" 503 1086 > > 192.168.2.3 - - [16/Mar/2009:16:07:48 +0100] "REMOVE-APP / HTTP/1.0" 200 - > > 192.168.2.3 - - [16/Mar/2009:16:07:48 +0100] "STATUS / HTTP/1.0" 200 59 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record?destroy=true HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:49 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 192.168.2.3 - - [16/Mar/2009:16:07:49 +0100] "STATUS / HTTP/1.0" 200 59 > > 192.168.2.3 - - [16/Mar/2009:16:07:50 +0100] "STATUS / HTTP/1.0" 200 59 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record?destroy=true HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 200 21 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 > > 127.0.0.1 - - [16/Mar/2009:16:07:51 +0100] "GET /load-demo/record HTTP/1.1" 404 999 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-193) mod_cluster 1.1.0 docs step 11.1.4.3 is wrong

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-193?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-193. ------------------------------------- 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 > mod_cluster 1.1.0 docs step 11.1.4.3 is wrong > --------------------------------------------- > > Key: MODCLUSTER-193 > URL: https://issues.jboss.org/browse/MODCLUSTER-193 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.Final > Reporter: Samuel Mendenhall > Assignee: Jean-Frederic Clere > Fix For: 1.0.8, 1.1.1.Final > > > http://docs.jboss.org/mod_cluster/1.1.0/html/UsingSSL.html > Section: 11.1.4.3. Create the client certificate > Step 2 > ================================== > mkdir -p CERTS/Client > cd CERTS/Client > ================================== > This is incorrect, it is the copy of step 1 instead of how to actually "Create a new request and sign it for the client certificate and key of the JBossWEB part." -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-26) Setup automated testing in Hudson

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-26?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-26. ------------------------------------ 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 automated testing in Hudson > --------------------------------- > > Key: MODCLUSTER-26 > URL: https://issues.jboss.org/browse/MODCLUSTER-26 > 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)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-187) ModClusterListener not working with Embedded Tomcat 6

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-187?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-187. ------------------------------------- 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 > ModClusterListener not working with Embedded Tomcat 6 > ----------------------------------------------------- > > Key: MODCLUSTER-187 > URL: https://issues.jboss.org/browse/MODCLUSTER-187 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.Final > Reporter: Galder Zamarreño > Assignee: Paul Ferraro > Attachments: TomcatContainer.java > > > ModClusterListener does not work with embedded Tomcat. > The listener does not seem to get called and hence it does not connect to mod_cluster httpd proxy. -- 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