[
http://issues.apache.org/jira/browse/XALANJ-1673?page=comments#action_12361203
]
Hari commented on XALANJ-1673:
------------------------------
The following is the comment provided in the corresponding Bugzilla page. I am
facing exactly the same issue.
Can you someone tell me if this issue will be resolved if I upgrade to 2.7
========================================================================
Hi,
I am from Sun Microsystems and we are using XALAN for XSL processing. Our
application is apparently observing good heap size increase. Using JProbe
analysis tool, I find couple of objects collecting in xsl processing -
org.apache.xpath.axes.AxesWalker ->
org.apache.xml.dtm.ref.DTMDefaultBaseTraversers$RootTraverser ->
org.apache.xml.dtm.ref.dom2dt.DOM2DTM -> Vector -> Object[] ->
AttrImpl/ElementImpl etc.
I am not sure what part of our code would result in that. We are using following
code for XSL transformation -
Transformer transformer = null;
if (xmlDoc == null) {
throw new XSLProcessingException("XSLProcessor: xmlDoc null");
}
if (outputStream == null)
throw new XSLProcessingException("XSLProcessor: outputStream null");
try {
transformer = _templates.newTransformer();
} catch (TransformerConfigurationException tce) {
throw new XSLProcessingException("XSLProcessor: transformer could not be
created : "
+tce.getMessage());
}
if (transformer == null) {
throw new XSLProcessingException("XSLProcessor: _transformer null");
}
try {
transformer.transform( new DOMSource(xmlDoc),
new StreamResult(outputStream));
} catch (TransformerException te) {
throw new XSLProcessingException("XSLProcessor: transform failed ("
+te.getMessage() + ")");
}
}
I suspect the bug raised here is what is resulting in heap size to increase.
When would we have a fix for this bug. It's quite urgent for us as our
application is released and the problem is reported by a customer.
==================================================================================
> "Memory leak" in xpath evaluations
> ----------------------------------
>
> Key: XALANJ-1673
> URL: http://issues.apache.org/jira/browse/XALANJ-1673
> Project: XalanJ2
> Type: Bug
> Components: XPath
> Versions: 2.5Dx
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: Tim Butcher
> Assignee: Xalan Developers Mailing List
>
> Java heap memory is used up whenever evaluating an xpath expression on a DOM
> Document.
> The 'leakage' goes away if the following lines in the constructor
> XPathResultImpl(short type, XObject result, Node contextNode)
> (XPathResultImpl.java) are commented out:
> if (((m_resultType == XPathResult.ORDERED_NODE_ITERATOR_TYPE) ||
> (m_resultType == XPathResult.UNORDERED_NODE_ITERATOR_TYPE))&&
> (contextNode instanceof EventTarget)) {
>
> ((EventTarget)contextNode).addEventListener("MutationEvents",this,true);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
