felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4422) Remove asynchronous starting of Jetty service
Date Wed, 12 Feb 2014 17:02:22 GMT

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

J.W. Janssen resolved FELIX-4422.

    Resolution: Fixed

Made the starting & stopping of synchronous in rev #1567677. All itests still work, and
some initial smoke tests in a real-world application does not show any problems.

> Remove asynchronous starting of Jetty service
> ---------------------------------------------
>                 Key: FELIX-4422
>                 URL: https://issues.apache.org/jira/browse/FELIX-4422
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>    Affects Versions: http-2.2.2
>            Reporter: J.W. Janssen
>             Fix For: http-2.3.0
> 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.

This message was sent by Atlassian JIRA

View raw message