Uploaded image for project: 'Edgent'
  1. Edgent
  2. EDGENT-439

optionally specify TCP port for Jetty HTTP server in console

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • Apache Edgent 1.1.0
    • Apache Edgent 1.3.0
    • Console
    • None

    Description

      In org.apache.edgent.console.server.HttpServer, the server port is hardwired to "0", so Jetty chooses a random port number each time it starts. This is a problem when Edgent runs in a Docker container. By default, Docker blocks access to all ports in a container. Port access can be enabled for a specific port by number when a container is created, but not after it has started running.

      Perhaps Edgent could honor a port number if specified with "java -Djetty.http.port=8080 ...", or use "0" if not.

      Attachments

        Activity

          People

            dlaboss Dale LaBossiere
            ejpring Edward Pring
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: