August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-81) MP Health reports UP when there is port collision for port 8080

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-81?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda reassigned WFWIP-81: -------------------------------------- Assignee: Jeff Mesnil (was: Kabir Khan) > MP Health reports UP when there is port collision for port 8080 > --------------------------------------------------------------- > > Key: WFWIP-81 > URL: https://issues.jboss.org/browse/WFWIP-81 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > MP Health reports UP when there is port collision for port 8080. > I have simple python app to acquire port 8080 and once it runs I start WF server > {code} > import SimpleHTTPServer > import SocketServer > PORT = 8080 > Handler = SimpleHTTPServer.SimpleHTTPRequestHandler > httpd = SocketServer.TCPServer(("127.0.0.1", PORT), Handler) > print "serving at port", PORT > httpd.serve_forever() > {code} > WF reports Address already in use /127.0.0.1:8080, deployments are not deployed. > Accessing http://localhost:9990/health/ reports "outcome":"UP" > I think this is wrong and DOWN should be reported. > Spec is misleading because it says {{A producer without health check procedures installed MUST returns positive overall outcome (i.e. HTTP 200)}} but it silently assumes server started correctly. > I believe authors of the spec expected that if there is some trouble like port collision the server doesn't start, WildFly is a bit further as it allows to boot even if some services are not started properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-81) MP Health reports UP when there is port collision for port 8080

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFWIP-81: -------------------------------------- Summary: MP Health reports UP when there is port collision for port 8080 Key: WFWIP-81 URL: https://issues.jboss.org/browse/WFWIP-81 Project: WildFly WIP Issue Type: Bug Reporter: Rostislav Svoboda Assignee: Kabir Khan Priority: Critical MP Health reports UP when there is port collision for port 8080. I have simple python app to acquire port 8080 and once it runs I start WF server {code} import SimpleHTTPServer import SocketServer PORT = 8080 Handler = SimpleHTTPServer.SimpleHTTPRequestHandler httpd = SocketServer.TCPServer(("127.0.0.1", PORT), Handler) print "serving at port", PORT httpd.serve_forever() {code} WF reports Address already in use /127.0.0.1:8080, deployments are not deployed. Accessing http://localhost:9990/health/ reports "outcome":"UP" I think this is wrong and DOWN should be reported. Spec is misleading because it says {{A producer without health check procedures installed MUST returns positive overall outcome (i.e. HTTP 200)}} but it silently assumes server started correctly. I believe authors of the spec expected that if there is some trouble like port collision the server doesn't start, WildFly is a bit further as it allows to boot even if some services are not started properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-80) Log warning when MP Health reports DOWN

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFWIP-80: -------------------------------------- Summary: Log warning when MP Health reports DOWN Key: WFWIP-80 URL: https://issues.jboss.org/browse/WFWIP-80 Project: WildFly WIP Issue Type: Enhancement Components: MP Health Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Enhance MP Health functionality to log warning when MP Health reports DOWN. This can be useful when working on investigation / retrospective analysis. Open Liberty prints following warning when http://localhost:9080/health reports DOWN {code} [WARNING ] CWMH0051W: The class com.ibm.ws.microprofile.health.impl.HealthCheckResponseImpl implementing HealthCheckResponse in the microprofile-health application in module microprofile-health.war, reported a DOWN outcome DOWN with data Optional[{availability=not available}]. {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10794) Include custom external modules directory in JDR

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-10794: ----------------------------------- Summary: Include custom external modules directory in JDR Key: WFLY-10794 URL: https://issues.jboss.org/browse/WFLY-10794 Project: WildFly Issue Type: Enhancement Components: JDR Affects Versions: 13.0.0.Final Reporter: Brad Maxwell Assignee: Brad Maxwell Include custom external modules directory in JDR. If Wildfly is running or running in embedded mode and an external that can be determined such as via the environment variable JBOSS_MODULEPATH, then include it when grabbing the module.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; should be ramping-up

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Summary: New mod_cluster nodes can become overloaded; should be ramping-up (was: New mod_cluster nodes can become overloaded; support ramping-up) > New mod_cluster nodes can become overloaded; should be ramping-up > ----------------------------------------------------------------- > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Add support for MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; support ramp-up when

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Summary: New mod_cluster nodes can become overloaded; support ramp-up when (was: Support ramp-up when starting new nodes (MODCLUSTER-449)) > New mod_cluster nodes can become overloaded; support ramp-up when > ----------------------------------------------------------------- > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Add support for MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; support ramp-up

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Summary: New mod_cluster nodes can become overloaded; support ramp-up (was: New mod_cluster nodes can become overloaded; support ramp-up when) > New mod_cluster nodes can become overloaded; support ramp-up > ------------------------------------------------------------ > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Add support for MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10769) New mod_cluster nodes can become overloaded; support ramping-up

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10769?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10769: ---------------------------------- Summary: New mod_cluster nodes can become overloaded; support ramping-up (was: New mod_cluster nodes can become overloaded; support ramp-up) > New mod_cluster nodes can become overloaded; support ramping-up > --------------------------------------------------------------- > > Key: WFLY-10769 > URL: https://issues.jboss.org/browse/WFLY-10769 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Add support for MODCLUSTER-449. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9232) mod_cluster decay factor does not support floating-point numerals, decays too quickly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9232?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9232: --------------------------------- Summary: mod_cluster decay factor does not support floating-point numerals, decays too quickly (was: Support floating-point numerals for mod_cluster decay factor) > mod_cluster decay factor does not support floating-point numerals, decays too quickly > ------------------------------------------------------------------------------------- > > Key: WFLY-9232 > URL: https://issues.jboss.org/browse/WFLY-9232 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 11.0.0.Beta1, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Downstream counterpart MODCLUSTER-607. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9232) mod_cluster decay factor does not support floating-point numerals; decays too quickly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9232?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9232: --------------------------------- Summary: mod_cluster decay factor does not support floating-point numerals; decays too quickly (was: mod_cluster decay factor does not support floating-point numerals, decays too quickly) > mod_cluster decay factor does not support floating-point numerals; decays too quickly > ------------------------------------------------------------------------------------- > > Key: WFLY-9232 > URL: https://issues.jboss.org/browse/WFLY-9232 > Project: WildFly > Issue Type: Enhancement > Components: mod_cluster > Affects Versions: 11.0.0.Beta1, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Downstream counterpart MODCLUSTER-607. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018