[
http://issues.ops4j.org/browse/PAXWEB-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12135#action_12135
]
Heiko Seeberger commented on PAXWEB-126:
----------------------------------------
For me (who raised this issue) it is not important to register multiple
connectors. Hence, if specifying 0 as the port and letting Jetty find a free
one, sounds great for me. The only thing missing is publishing the used port as
a service property, but Alin is working on that for 0.5.3
> Pax Web should find a free port and use it
> ------------------------------------------
>
> Key: PAXWEB-126
> URL: http://issues.ops4j.org/browse/PAXWEB-126
> Project: Pax Web
> Issue Type: New Feature
> Reporter: Heiko Seeberger
> Assignee: Alin Dreghiciu
> Fix For: 0.5.3
>
>
> Currently the port for the HttpService is specified via System property or
> Config Admin service. The latter offers a lot of flexibility, but even then
> it may happen that the given port is not "free".
> Therefore it would be valuable if Pax Web would scan/try for free ports until
> if can find and use one.
> I am not sure what would be the best strategy. The most simple one would
> increrase port numbers starting from the default port or the one specified
> via the System property or Config Admin. But maybe it could make sense to
> have a "port scan service" which produces and remembers the port numbers and
> has additional methods to get the used/successful port number for any given
> Http Service (maybe identified by service id).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
