[jboss-jira] [JBoss JIRA] (WFLY-10864) MP Health reports UP when there is port collision for port 8080
Rostislav Svoboda (JIRA)
issues at jboss.org
Thu Aug 16 04:28:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rostislav Svoboda moved WFWIP-81 to WFLY-10864:
-----------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-10864 (was: WFWIP-81)
Component/s: MP Health
(was: MP Health)
> MP Health reports UP when there is port collision for port 8080
> ---------------------------------------------------------------
>
> Key: WFLY-10864
> URL: https://issues.jboss.org/browse/WFLY-10864
> Project: WildFly
> 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)
More information about the jboss-jira
mailing list