[
https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942271#comment-13942271
]
Felix Meschberger edited comment on FELIX-4460 at 3/20/14 9:05 PM:
-------------------------------------------------------------------
Fixed in Rev. 1579733 & 1579739:
* Start connectors individually after the server start
* Stop the server if no connector can be started
was (Author: fmeschbe):
Fixed in Rev. 1579733:
* Start connectors individually after the server start
* Stop the server if no connector can be started
> Bad HTTPS settings render Jetty inaccessible
> --------------------------------------------
>
> Key: FELIX-4460
> URL: https://issues.apache.org/jira/browse/FELIX-4460
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Affects Versions: http-2.2.2
> Reporter: Dominique Pfister
> Assignee: Felix Meschberger
> Fix For: http-2.3.0
>
> Attachments: patch.txt
>
>
> Entering some bad values for the HTTPS configuration prevents the complete
> Jetty server startup. This looks like a regression of upgrading Jetty to
> version 7.
> The current implementation initializes all enabled connectors, adds them to
> the server and then starts the server which in turn starts all connectors. If
> one of them fails to start, the complete server startup fails and the Jetty
> Bridge is no longer accessible via HTTP.
> I suggest to initialize an additional HTTPS connector only after having
> started the server, so at least HTTP stays available if enabled.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
