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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] OS/Version|Other |All Priority|Other |High Platform|Other |All ------- Additional Comments From [EMAIL PROTECTED] 2004-03-31 11:06 ------- Thank you for catching that problem! I hadn't thought about the fact that the Hashtable would continue to hold a reference to an XMLReader even after the only thread that will use that XMLReader has ceased to exist. There are circumstances in which a thread will have more than one transformation and more than one XMLReader active at one time. The Hashtable was intended to prevent a thread from attempting to use the same XMLReader in two different places at one time. I will instead use a second ThreadLocal variable to keep track of whether an XMLReader is in use.
