You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Anis Moussa (JIRA)" <xa...@xml.apache.org> on 2008/07/10 14:48:31 UTC
[jira] Commented: (XALANJ-2450) Revision 337966 needed in XalanJ
2.4.1
(http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFrag.java?view=log)
[ https://issues.apache.org/jira/browse/XALANJ-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612471#action_12612471 ]
Anis Moussa commented on XALANJ-2450:
-------------------------------------
Hi ,
the memleak is caused by the XRTreeFrag objects were created.
It took too long for finalizer to be executed to release the references.
analysing the JRA traces from JRockit JVM and the verbose traces
it is clear that it is the memory leak you are hunting
that is causing trouble. It looks like the leak is coming from the XRTreeFrag
class.
I found the following post on apache's pages which seems to be the problem.
http://issues.apache.org/jira/browse/XALANJ-2128
The issue is fixed in version 2.7 of Xalan so it really has nothing to do
with JRockit.
if it's possible, the same issue could be fixed on the release 2.4.1 of Xalan ?
below the bug reference that have been fixed in release 2.7
http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFrag.java?view=log
http://svn.apache.org/viewvc?view=rev&revision=337966
Cheers,
Anis
> Revision 337966 needed in XalanJ 2.4.1 (http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFrag.java?view=log)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XALANJ-2450
> URL: https://issues.apache.org/jira/browse/XALANJ-2450
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects. Anybody can view the issue.)
> Components: Xalan
> Affects Versions: 2.4
> Environment: Red Hat Linux AS/ES 4.0, WebLogic 8.1 with Service Pack 4, Apache Web Server 2.0.55, Tomcat Java Servlet Server 5.5.16, JRockit JDK 1.4.2_16
> Reporter: Kristof Stevens
> Priority: Critical
> Fix For: 2.4
>
>
> We are facing a Memory Leak issue on our OTM Webserver because of this issue. BEA Support suggested to upgrade Xalan version to 2.7 but our software OTM (Oracle Transportation Management) is not supporting higher version than Xalan 2.4.1.
> 1) The patch on Xalan 2.7 is not compatible with 2.4.1
> 2) OTM will not work with any other version of Xalan (at the moment) other than 2.4.1 due to a dependency on the class org.apache.xalan.xlstc.runtime.DefaultSAXOutputHandler which was removed as of 2.5.x
> 3) I am not sure if DefaultSAXOutputHandler will work with the latest Xalan.
> FR: amoussa
>
> CASE_ID_NUM: 771668
> CASE TITLE: WLJR 1.4.2 - MemLeak tool crashing
>
> MESSAGE:
> Dear Kristof ,
> As Xalan is not provided by BEA Systems , we don't support such product, if this Api was delivered by BEA in Jrockit product ,
> then , I will be able to open a support case with Apache to handle that.
> Below the description of the bug :
> http://svn.apache.org/viewvc/xalan/java/tags/xalan-j_2_7_0/src/org/apache/xpath/objects/XRTreeFrag.java?view=log
> http://svn.apache.org/viewvc?view=rev&revision=337966
> please kindly try to understand what I'm suppose to do here , this become out of my scope .
> Best Regards
> Anis
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org