[
https://issues.apache.org/jira/browse/XALANJ-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610932#action_12610932
]
Michel Loiseleur commented on XALANJ-2178:
------------------------------------------
Hi,
We have made a fix which works well for this memory leak (more than 6 months
without any memory leak). Feel free to apply it and include it in 2.7.0 code
base. It's the same one than the issue 2195, since it's the same problem.
Regards,
> Possible memory leak in XMLReaderManager
> ----------------------------------------
>
> Key: XALANJ-2178
> URL: https://issues.apache.org/jira/browse/XALANJ-2178
> Project: XalanJ2
> Issue Type: Bug
> Components: transformation
> Affects Versions: 2.7, 2.6
> Reporter: Carsten Ziegeler
> Priority: Critical
> Attachments: xalan-j2-2.6.0-xmlmemoryleak-tm2l.patch,
> XMLReaderManager.java
>
>
> The XMLReaderManager caches the used XMLReader in a thread local variable. In
> multi tasking environments this is a possible memory leak, as the XMLReader
> (and everything referenced by this component) is still referenced after the
> process is finished - until another request uses the same thread.
> In our case this is causing out of memory exceptions.
> I don't know what the correct path to this problem is. For now, we removed
> the thread locals in the XMLReaderManager completly and created a new reader
> each time - which has a minor performance downside, but our application is
> still running :)
> I think one possible solution would be to clean up the reader when the
> transformation is finished - if this is possible.
> Another solution would be to make this configurable using a property?
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
