| Leak Suspects org.apache.xalan.templates.ElemTemplate [message #8705] |
Tue, 10 February 2009 11:59  |
Eclipse User |
|
|
|
I run memory-analyzer on a dump from production environment created on
OutOfMemoryError.
As first report I choose Memory Leak Suspect and it shows me two classes:
- org.apache.xalan.templates.ElemTemplate 29.155 instances occupy
227.620.440 (44,99%) bytes
and
- org.apache.xerces.parsers.SAXParser 164 instances occupy 57.489.064
(11,36%) bytes.
Our application is a Web servlet use Xalan 2.6.0 tranformer to render HTML
pages from xml data.
Does anybody have such an error?
How can I investigate more?
Thanks in advance, Matteo.
|
|
|
| Re: Leak Suspects org.apache.xalan.templates.ElemTemplate [message #8731 is a reply to message #8705] |
Wed, 11 February 2009 05:09  |
| Eclipse User |
|
|
|
Hi Matteo,
Is it expected that the parsers are kept by the application or not? If you
want/need to keep them, then I guess you will have to accept the "cost"
and try to re-arrange the memory settings of the server.
If you didn't expect these instances to be kept, then you can have a look
at the paths from GC roots, to figure out who is keeping them in memory.
In the generated report, there should be details for every suspect.
Normally, there (in the detaills) you should find already summarized info
about the paths from the GC roots to the suspect objects. In your case,
you should be able to see the common part of the paths to each of the
SAXParsers / ElemTemplates. Have you lookead at this already? Does it help
you?
Regards,
Krum
|
|
|
Powered by
FUDForum. Page generated in 0.26863 seconds
Home