DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28082>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28082 XMLReaderManager provides neither no way to clear its cache nor it clears its cache by itself ------- Additional Comments From [EMAIL PROTECTED] 2004-04-27 18:38 ------- The previous attachement (id=11360) is is a version of XMLReaderManager that uses a thread-local stack to track available readers. Since the stack contains only available readers, they are, by definition, not "in use". Thus, the "in use" map can be eliminated, which fixes the memory leak issue created by that map. It still may be better to use a cross-thread pool of available readers with a clean-up thread that periodically discards cached readers that have been idle too long. This implementation still has the potential for a long-lived thread to build up many cached readers that are not longer needed without a way to clean them up, but at least they will not persist once owner thread dies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
