On 1 Oct 2010, at 08:30, Felix Meschberger wrote: >> >> Inside the javax.servlet.HttpServlet code, probably part of Jetty/PAX, >> AFAICT, I am not certain I believe the stack trace is complete from YourKit >> (might have holes in it) > > Wow! I know see ... They have the javax.servlet.HttpServlet.class > mechanism --- and we have it, too, in the SlingAllMethodsServlet .... > > Should we (for the SlingAllMethodsServlet) do something about it ? >
If you mean the calls to getClass(), we could cache the class early on and once, but I didn't see any problems with that code in my tests. It was the ServletHolders use of Loader.loadClass that was falling through to Class.forName inside Jetty. AFAICT, changing the thread pool configuration in Jetty might eliminate this as I think this only happens as threads come and go with new servlets. Ian > Regards > Felix > >> >> >> >>> >>> Regards >>> Felix >>> >>>> >>>> ItemManager has blocked, but only 161 times, >>>> >>>> So my problems are caused by something I have done outside Sling in my own >>>> code, almost certainly related to sharing a Session between threads. >>>> Sorry for causing alarm (if I did). >>>> >>>> Ian >>>> >>>>> >>>>> Which means that a session is being shared between threads, making it >>>>> block threads ? >>>>> Does that make sense ? >>>>> Ian >>>>> >>>>> >>>> >>>> >> >>
