Chris,
As I have mentioned earlier, I have following code in one of the
"finally" blocks.
Field dbfield =
ReflectionUtil.getDeclaredField(XMLUtils.class,
"documentBuilder");
ThreadLocal db = (ThreadLocal) dbfield.get(null);
if (db !=
Pid,Chris
Thanks for your reponses. Meanwhile, I have come up with the following
code in the app to clear threadlocals for a thread. I have a
ReflectionUtil class that actually sets the accessible to true on the
Field after obtaining it via reflection.
-
On 13/12/2010 20:56, Ebert, Chris wrote:
> I haven't solved this specific issue but (when the object isn't directly
> accessible, which I assume is the case) you could:
>
> 1) find the nearest accessible object to the field you want.
> 2) get the field value using reflection, setting accessibilit
I haven't solved this specific issue but (when the object isn't directly
accessible, which I assume is the case) you could:
1) find the nearest accessible object to the field you want.
2) get the field value using reflection, setting accessibility if need be.
3) Do what you need to: clear the thr
On 13/12/2010 02:31, Srikanth Konjarla wrote:
> All,
>
> I have a webapp that uses Axis 1.4 as client. I see few ThreadLocal
> forcible removed error messages in tomcat log file during undeploy
> process of the application which suggests me that there exists some kind
> of memory leak due to the w
All,
I have a webapp that uses Axis 1.4 as client. I see few ThreadLocal
forcible removed error messages in tomcat log file during undeploy
process of the application which suggests me that there exists some kind
of memory leak due to the way certain ThreadLocals are handled by Axis
1.4. Here are
