felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FELIX-4460) Bad HTTPS settings prevent startup HTTP listener
Date Sun, 16 Mar 2014 13:16:45 GMT
Dominique Pfister created FELIX-4460:

             Summary: 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

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 container only after having the server, so at
least HTTP stays available if enabled.


This message was sent by Atlassian JIRA

View raw message