Hi, On Tue, Nov 30, 2010 at 1:20 PM, Vidar Ramdal <vi...@idium.no> wrote: >>... There is also a large number of lines saying *INFO* [SCR Component >> Actor] org.apache.sling.servlets.resolver >> [org.apache.sling.servlets.resolver.SlingServletResolver] Dependency >> not satisfied: servletContext > > Digging around, I see that o.a.felix.http.jetty.internal.JettyService > is started, the thread's run method is invoked, but then almost > immediately interrupted from the updated method, when JettyService > receives its configuration. > This again triggers initializeJetty(), which calls new Server()....
I don't have a solution but FWIW I've also seen this behavior in testing framework startup: components are activated, deactivated and reactivated quickly as the framework tries to startup things and fails because not all required components are available. From what you're seeing it seems like the JettyService does not handle this scenario correctly. -Bertrand
