December 2014 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-431) MulticastSocketFactoryImplTestCase.testMulticastSocketAllowCrossTalk doesn't work since JDK 1.8

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-431?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-431: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged. > MulticastSocketFactoryImplTestCase.testMulticastSocketAllowCrossTalk doesn't work since JDK 1.8 > ----------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-431 > URL: https://issues.jboss.org/browse/MODCLUSTER-431 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.2.10.Final, 1.3.1.Alpha3 > > > Since crosstalking no longer happens on Linux since JDK 8. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-431) MulticastSocketFactoryImplTestCase.testMulticastSocketAllowCrossTalk doesn't work since JDK 1.8

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-431?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-431: -------------------------------------- Fix Version/s: 1.2.10.Final > MulticastSocketFactoryImplTestCase.testMulticastSocketAllowCrossTalk doesn't work since JDK 1.8 > ----------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-431 > URL: https://issues.jboss.org/browse/MODCLUSTER-431 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.2.10.Final, 1.3.1.Alpha3 > > > Since crosstalking no longer happens on Linux since JDK 8. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-431) MulticastSocketFactoryImplTestCase.testMulticastSocketAllowCrossTalk doesn't work since JDK 1.8

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-431?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-431: -------------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/117, https://github.com/modcluster/mod_cluster/pull/124 (was: https://github.com/modcluster/mod_cluster/pull/117) > MulticastSocketFactoryImplTestCase.testMulticastSocketAllowCrossTalk doesn't work since JDK 1.8 > ----------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-431 > URL: https://issues.jboss.org/browse/MODCLUSTER-431 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.2.9.Final, 1.3.1.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.2.10.Final, 1.3.1.Alpha3 > > > Since crosstalking no longer happens on Linux since JDK 8. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-416) mod_cluster Connected count shows improper inflation

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-416?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-416: ------------------------------------------- Just noting that partially fixed/mitigated in 1.2.10.Final, 1.3.1.Alpha3. Further work needed. > mod_cluster Connected count shows improper inflation > ---------------------------------------------------- > > Key: MODCLUSTER-416 > URL: https://issues.jboss.org/browse/MODCLUSTER-416 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Alpha3 > > > The mod_cluster connected count (a proxy_worker's busy attribute) shows improper inflation. With load stopped, non-zero values have still been seen through the mod_cluster-manager page and INFO MCMP responses. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-408: -------------------------------------- Component/s: Native (httpd modules) (was: Core & Container Integration (Java)) > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Alpha1 > > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-408: -------------------------------------- Component/s: Core & Container Integration (Java) > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Alpha1 > > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-408: ------------------------------------------- Also made it to 1.3.1.Alpha1. > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Alpha1 > > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-408: -------------------------------------- Fix Version/s: 1.3.1.Alpha1 > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final, 1.3.1.Alpha1 > > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-408: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done This was already merged. > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final > > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-408: -------------------------------------- Fix Version/s: 1.2.10.Final > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.10.Final > > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues December 2014