felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4460) Bad HTTPS settings render Jetty inaccessible
Date Thu, 20 Mar 2014 21:03:44 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Felix Meschberger resolved FELIX-4460.

       Resolution: Fixed
    Fix Version/s: http-2.3.0

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

View raw message