March 2018 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-646) Remove deprecation compiler warnings for MCMPHandler#addProxy(java.net.InetSocketAddress) usage

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-646?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-646: ----------------------------------------- Assignee: Radoslav Husar (was: Jean-Frederic Clere) > Remove deprecation compiler warnings for MCMPHandler#addProxy(java.net.InetSocketAddress) usage > ----------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-646 > URL: https://issues.jboss.org/browse/MODCLUSTER-646 > Project: mod_cluster > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {noformat} > [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/advertise/impl/AdvertiseListenerImpl.java:[308,67] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated > [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/mcmp/impl/DefaultMCMPHandler.java:[218,17] addProxy(java.net.InetSocketAddress,boolean) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated > [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/mcmp/impl/DefaultMCMPHandler.java:[167,17] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated > [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/ModClusterService.java:[415,25] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated > [WARNING] /Users/rhusar/git/mod_cluster/core/src/test/java/org/jboss/modcluster/advertise/impl/AdvertiseListenerImplTestCase.java:[101,62] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated > [WARNING] /Users/rhusar/git/mod_cluster/core/src/test/java/org/jboss/modcluster/advertise/impl/AdvertiseListenerImplTestCase.java:[116,62] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-646) Remove deprecation compiler warnings for MCMPHandler#addProxy(java.net.InetSocketAddress) usage

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-646: ----------------------------------------- Summary: Remove deprecation compiler warnings for MCMPHandler#addProxy(java.net.InetSocketAddress) usage Key: MODCLUSTER-646 URL: https://issues.jboss.org/browse/MODCLUSTER-646 Project: mod_cluster Issue Type: Task Reporter: Radoslav Husar Assignee: Jean-Frederic Clere {noformat} [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/advertise/impl/AdvertiseListenerImpl.java:[308,67] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/mcmp/impl/DefaultMCMPHandler.java:[218,17] addProxy(java.net.InetSocketAddress,boolean) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/mcmp/impl/DefaultMCMPHandler.java:[167,17] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated [WARNING] /Users/rhusar/git/mod_cluster/core/src/main/java/org/jboss/modcluster/ModClusterService.java:[415,25] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated [WARNING] /Users/rhusar/git/mod_cluster/core/src/test/java/org/jboss/modcluster/advertise/impl/AdvertiseListenerImplTestCase.java:[101,62] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated [WARNING] /Users/rhusar/git/mod_cluster/core/src/test/java/org/jboss/modcluster/advertise/impl/AdvertiseListenerImplTestCase.java:[116,62] addProxy(java.net.InetSocketAddress) in org.jboss.modcluster.mcmp.MCMPHandler has been deprecated {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-645) Different handling of max-attempts parameter on Undertow and httpd implementation

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-645?page=com.atlassian.jira.pl... ] Jan Kašík updated MODCLUSTER-645: --------------------------------- Description: The behavior of balancer is different on httpd in comparsion with Undertow implementation when max-attempts parameter is set. * *Undertow*: max-attempts is total count of requests made by balancer in failover scenario. When max-attemps is set to 1 and target worker fails after first attempt made by balancer, no further attempts are made. * *httpd*: max-attempts is count of retries made by balancer after first attempt fails. When max-attempts is set to 1 and target worker fails after first attempt made by balancer, second worker is chosen and request is sent towards it. This doesn't seem right and I suggest to unify behavior across implementations. was: The behavior of balancer is different on httpd in comparsion with Undertow implementation when max-attempts parameter is set. * *Undertow*: max-attempts is total count of requests made by balancer in failover scenario. When max-attemps is set to 1 and target worker fails after first attempt made by balancer, no further attempts are made. * *httpd*: max-attempts is count of retries made by balancer after first attempt fails. When max-attempts is set to 1 and target worker fails after first attempt made by balancer, second worker is chosen and request is send towards it. This doesn't seem right and I suggest to unify behavior across implementations. > Different handling of max-attempts parameter on Undertow and httpd implementation > --------------------------------------------------------------------------------- > > Key: MODCLUSTER-645 > URL: https://issues.jboss.org/browse/MODCLUSTER-645 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.5.Final > Reporter: Jan Kašík > Assignee: Jean-Frederic Clere > > The behavior of balancer is different on httpd in comparsion with Undertow implementation when max-attempts parameter is set. > * *Undertow*: max-attempts is total count of requests made by balancer in failover scenario. When max-attemps is set to 1 and target worker fails after first attempt made by balancer, no further attempts are made. > * *httpd*: max-attempts is count of retries made by balancer after first attempt fails. When max-attempts is set to 1 and target worker fails after first attempt made by balancer, second worker is chosen and request is sent towards it. > This doesn't seem right and I suggest to unify behavior across implementations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-645) Different handling of max-attempts parameter on Undertow and httpd implementation

by Jan Kašík (JIRA)

Jan Kašík created MODCLUSTER-645: ------------------------------------ Summary: Different handling of max-attempts parameter on Undertow and httpd implementation Key: MODCLUSTER-645 URL: https://issues.jboss.org/browse/MODCLUSTER-645 Project: mod_cluster Issue Type: Bug Affects Versions: 1.3.5.Final Reporter: Jan Kašík Assignee: Jean-Frederic Clere The behavior of balancer is different on httpd in comparsion with Undertow implementation when max-attempts parameter is set. * *Undertow*: max-attempts is total count of requests made by balancer in failover scenario. When max-attemps is set to 1 and target worker fails after first attempt made by balancer, no further attempts are made. * *httpd*: max-attempts is count of retries made by balancer after first attempt fails. When max-attempts is set to 1 and target worker fails after first attempt made by balancer, second worker is chosen and request is send towards it. This doesn't seem right and I suggest to unify behavior across implementations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-643) Misleading JavaDoc for SPI Container Engine

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-643?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-643: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/317 > Misleading JavaDoc for SPI Container Engine > ------------------------------------------- > > Key: MODCLUSTER-643 > URL: https://issues.jboss.org/browse/MODCLUSTER-643 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.8.Final, 1.4.0.Alpha1 > Reporter: Michal Herda > Assignee: Radoslav Husar > Priority: Trivial > > https://github.com/modcluster/mod_cluster/blob/7e4dadf03df78f05bbf06af698... > {code} > /** > * The connector to which this engine uses to communicate with its proxies. > * > * @return the connector used by mod_cluster > */ > Connector getProxyConnector(); > /** > * The connector to which this engine uses to communicate with its proxies. > * > * @return the connector used by mod_cluster > */ > Iterable<Connector> getConnectors(); > {code} > From what I see and understand from the code, the javadoc for getConnectors() does not reflect its actual purpose - it seems like a copypaste from getProxyConnector(). I am not competent enough to write a proper JavaDoc myself through - please support me with it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues March 2018