Hi, Yes, we also experience this.
I have to track down the exact cause, but I suspect it is related to the new dynamic class loader and script caching: the classloader is replaced but scripts loaded with the old class loader are still used (mostly the JSP bundle is a candidate for this) and thus still try to access old classes, which have been replaced.... Regards Felix Vidar Ramdal schrieb: > I'm seeing a problem with the org.apache.sling.commons.classloader bundle. > When I update certain of my own bundles, RhinoJavaScriptEngineFactory > and JspScriptEngineFactory components are listed as unsatisfied in the > web console (see attached screenshot). This only happens with some of > my bundles, not all, but the problem seems to be reproducable always. > > In this state, all attempts to run a rendering script fails with 403 > Forbidden, as if the script does not exist. Let's say I have the > script /apps/page/GET.esp. > Before a bundle update, the script is invoked when I request > http://localhost:8080/node. After I update a bundle, the same URL > gives me 403 Forbidden, as if the script does not exist. > This seems to only apply to scripts, not servlets - > http://localhost:8080/node.html always gives me the default output by > HtmlRendererServlet. > > When this problem occurs, I restart the Dynamic Class Loader bundle, > and everything is back to normal - until I update one of my > problematic bundles again. > > I have yet to discover exactly what in my bundles is triggering this > error, but I'll investigate more. > > In the mean time, is anyone else seeing this problem? >
