Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-4422

Remove asynchronous starting of Jetty service

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • http-2.2.2
    • http-2.3.0
    • HTTP Service
    • None

    Description

      The Jetty bundle currently uses an ExecutorService to start Jetty in the background. I'm not sure this is actually needed with the recent versions of Jetty. I've did a quick test to start Jetty synchronously in the bundle activator, but could not measure any significant timing differences in startup times.

      A reason to change this is that it makes the start/stop behaviour bundle more deterministic when using it in integration tests.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. FELIX-4137 Web application bundle (WAB) deployment

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. FELIX-4423 ClassNotFoundException when stopping Jetty bundle

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              jajans J.W. Janssen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: