Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Sun, 16 Mar 2014 13:20:44 +0000 (UTC)
From: "Dominique Pfister (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12701738.1394975752233.85621.1394976044530@arcas>
In-Reply-To: <JIRA.12701738.1394975752233@arcas>
References: <JIRA.12701738.1394975752233@arcas>
Subject: [jira] [Updated] (FELIX-4460) Bad HTTPS settings prevent startup
 HTTP listener
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dominique Pfister updated FELIX-4460:
-------------------------------------

    Attachment: patch.txt

Patch to initialize auxiliary HTTPS connector only after having started the server.

> Bad HTTPS settings prevent startup HTTP listener
> ------------------------------------------------
>
>                 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
>         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)