Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10864

MP Health reports UP when there is port collision for port 8080

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Duplicate
    • Critical
    • 21.0.0.Beta1
    • None
    • MP Health
    • None

    Description

      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

      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()
      

      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.

      Attachments

        Issue Links

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              rsvoboda@redhat.com Rostislav Svoboda
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: