On Fri, Dec 6, 2013 at 10:46 AM, anjan <[email protected]> wrote: ... > Build #1676 (May 30, 2013 12:10:42 AM) > Revision: 1487628 ...
Ok, if you're seeing the problem described at [1] please create a jira issue, ideally with a scenario that allows us to reproduce the problem. In [1] Vidar analysed the problem as follows: "...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..." if you could confirm if it's what's happening in your case that would be perfect. You might also try to upgrade to more recent build, I don't remember myself seeing something like that fixed since May 30 but maybe we use a more recent version of the jetty service since that time, I haven't checked that. -Bertrand [1] http://apache-sling.73963.n3.nabble.com/Sling-sometimes-return-404-on-all-requests-after-startup-td1992032.html
