Is there no way for me to kill these?
Not easily. Most uses of ThreadLocal seem to be blissfully (sometimes
arrogantly) unaware of thread-pooling mechanisms and app servers. Ideally,
these ThreadLocal instances would instead be created in a pool for the webapp
to use, rather than being tied to individual threads.
6.0.26 removes those by default. 6.0.29, removing them is optional - see
the clearReferencesThreadLocals attribute on the context.
The only way to get rid of the messages is to fix the memory leak.
Other solution is to create a new thread by yourself and delegate the
iCal4j work to it. Once the thread is finished, ThreadLocal variables
are also released. We managed to work around similar leak in older
JasperReports library like that.
Be aware, however, that creation of threads takes some resources, and
that you should take necessary steps to clean up those threads in all
cases (when exception is thrown in the thread, or when the server shuts
down while your thread is still active).
Regards,
Ognjen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
