Select toString(info.workerThreadName), toString(.buff) from infoĪ thread with a lot of .* objects like BooleanQuery, BooleanScorer2, TermScorer: it can be an exploding query, meaning one that has too many hits, taking up too much memory while processing those.įor analysis, find the URL involved from the HstRequestContext to map it back to the page and components involved. Select * from .request.HstRequestContextImpl If supported by your tool, use OQL to list objects, see Įxamples: all HST Request Contexts, HST Requests, HST Managers, worker threads+requests: Search for RequestContextImpl objects using OQL if that is supported, see below. In its properties you will find what this request was, looking at the baseURL. Try to find a RequestContextImpl that has the same 'catalina-exec-xyz' as found earlier.
It should show the root object which is 'catalina-exec-xyz' if the object is part of an incoming request to a Tomcat, typically a browser request.Ģ) Match HST request context to the same HTTP request. Matching a big object to a URLġ) Match a big object to an HTTP request.įrom an object, use "Path to GC roots" function (or similar). If present, a CMS was deployed, else just a site/delivery tier. Some valuable properties are contained in the baseURL object within this class: Commonly tied to a 'catalina-exec' thread. request.HstRequestContextImpl, one for an HST request, typically from a browser. 1 or 2 instances only can be one for live and one for preview. They can be a couple of tens of MBs, depending on the HST configuration involved. model.HstManagerImpl objects contain the HST model. There should not be too many of them, some tens are normal. HippoLocalItemStateManager objects correspond to JCR sessions. Sizes up to 200MB are not ununsual, depending on data size and settings, e.g. Ĭorresponds to the repository, also known as the bundle cache. Examine the biggest objects: Dominators, Top Consumers, Leak Suspects that the tool provides.Į.g.When on Tomcat, a thread "catalina-exec-xyz" can be matched to a URL (see later). This can be a lead to figure out the cause, but not necessarily because the thread can also be just a tipping point.
Your tool may provide a thread in which an OOM happened.
0 kommentar(er)
