[jira] [Commented] (FELIX-4460) Bad HTTPS settings render Jetty inaccessible

["Felix Meschberger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942243#comment-13942243 ] 

Felix Meschberger commented on FELIX-4460:
------------------------------------------

Thanks for providing the patch. I actually took a different route: The server will be started at first and then the connectors will be started one after the other. Any connector not being able to start will prevent the other connector from starting. If neither connector can be started, the Jetty server itself is stopped again.

> 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
>         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)