[FELIX-4460] Bad HTTPS settings render Jetty inaccessible

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: http-2.2.2
• Fix Version/s: http-2.3.0
• Component/s: HTTP Service
• Assignee: Unassigned
• Reporter: Dominique Pfister
• Created: 16/Mar/14 13:15
• Updated: 13/Jun/14 09:23
• Resolved: 20/Mar/14 21:03

Description

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.