In a web application running in WebLogic, we are using a (commercial) library which doesn't free the ThreadLocal variables it uses. Each time a method in the library API is used, some Kbs of information are leaked in the Thread that processes the request.
We are in the way of getting rid of the library but, in the meantime, we would like to fix the leak which is eventually consuming all memory.
Creating a new thread which dies after the library call seems a good approach, but is there a 'standard' way to do so on Weblogic 10? (Work Managers doesn't seem to support it)
We could try to spawn a new Java process, but that will need more effort to be able to decouple the library from the web application.
Do you think of any other workaround?
Feel free to ask for more details, and thank you for your comments.