[ http://issues.apache.org/jira/browse/XALANJ-2178?page=comments#action_12356536 ]
Brian Minchau commented on XALANJ-2178: --------------------------------------- Carsten, does the XMLReaderManager.java file that you attached have a proposed fix in it? There were memory leak issues that were fixed in XMLReaderManager via other issues according to Henry Zongaro. So the question is, is this still a problem for you in the new 2.7.0 code? > Possible memory leak in XMLReaderManager > ---------------------------------------- > > Key: XALANJ-2178 > URL: http://issues.apache.org/jira/browse/XALANJ-2178 > Project: XalanJ2 > Type: Bug > Components: transformation > Versions: 2.6 > Reporter: Carsten Ziegeler > Priority: Critical > Attachments: 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. - 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]
