--- Comment #1 from Unlogic <unlogic@...> 2011-05-18 06:39:00 UTC ---
I checked out the code from the FOP 1.0 tag and looked at the
From what I can see this type of caching using ThreadLocal will not work well
any environment where thread pools are used and where applications can be
deployed and undeployed in runtime such as J2EE web applications.
A workaround until a fix is out is to create a new thread for each PDF
generation and the let the thread from the thread pool call the join() method
on the new thread. This resolves the memory leak but on other hand makes the
cache essentially pointless.