[
http://issues.ops4j.org/jira/browse/PAXWEB-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_10583
]
Toni Menzel commented on PAXWEB-9:
----------------------------------
For me there are two opposite forces if the port is already bound:
1.) since the service is all about serving the content through this port it can
be considered as not valid and thus just refuse to start until the port is
either reconfigured or free.
2.) since we are in a dynamic environment we could start and bind everything up
whatever is possible and try to bind the port automatically when it gets free
(this requires polling..)
In general this behaviour can be somewhat misleading because imagine you forget
you have a running paxweb which waits for 8080 to be free.. then you play with
your tomcat (which has 8080) stop and start it and wonder why this suddenly
fails.
because of this, i would prefer 1. because it is the more relyable way.
Maybe we can provide the second polling mode as an extra functionality (extra
bundle)
just my 2ct.
Toni
> handle the case that the configured port is in use
> --------------------------------------------------
>
> Key: PAXWEB-9
> URL: http://issues.ops4j.org/jira/browse/PAXWEB-9
> Project: Pax Web
> Issue Type: Task
> Reporter: Alin Dreghiciu
> Assignee: Alin Dreghiciu
>
> handle the case that by starting the server the configured ports are in use.
> What shall be done?
> * just log and do not start the server but keep the http service up?
> unregister the service?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
