[
https://issues.apache.org/jira/browse/EDGENT-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285430#comment-16285430
]
Dale LaBossiere commented on EDGENT-439:
----------------------------------------
with PR-331, the Edgent Console port can be overridden using the
"edgent.console.port" system property.
> optionally specify TCP port for Jetty HTTP server in console
> ------------------------------------------------------------
>
> Key: EDGENT-439
> URL: https://issues.apache.org/jira/browse/EDGENT-439
> Project: Edgent
> Issue Type: Bug
> Components: Console
> Affects Versions: Apache Edgent 1.1.0
> Reporter: Edward Pring
> Assignee: Dale LaBossiere
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
