[
https://issues.apache.org/jira/browse/FELIX-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899076#comment-13899076
]
J.W. Janssen commented on FELIX-4422:
-------------------------------------
[~dpfister] thanks for the info. Probably the earlier versions of Jetty started
synchronously and you needed to background it yourself. The latest version(s)
no longer need this. Is it necessary for the web-app support to deploy/undeploy
asynchronously (is it potentially time consuming to deploy this)?
> 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
(v6.1.5#6160)
