> 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()....
On Tue, Nov 30, 2010 at 1:34 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > 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. Thanks Bertrand! It seems (for now) that the problem can be made much less frequent by moving the o.a.f..http.whiteboard bundle to a lower start level. I'll give it some time and see if it helps. -- Vidar S. Ramdal <vi...@idium.no> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
