Re: [aspectj-dev] Question on WeavingAdaptor

[Andy Clement <andrew.clement@xxxxxxxxx>]

Hi,

First time I've heard of that error coming out.

I just raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=387122 to
track it.  There is no workaround that I am aware of to deal with it.
I know there are some tomcat settings to enable/disable clearing of
static state in classes, perhaps there are settings to clear
threadlocal?  The weaver isn't aware of the application lifecycle
under tomcat so it may be tricky to know when it is finished with and
the threadlocal can be wiped.

cheers,
Andy

On 12 August 2012 07:53, Glenn Marintes <gmarintes@xxxxxxxxx> wrote:
> Hi everyone,
>
> We have a web app with Spring and AspectJ LTW enabled.
>
> We are encountering:
> SEVERE: The web application [/] created a ThreadLocal with key of type
> [org.aspectj.weaver.tools.WeavingAdaptor$1] (value
> [org.aspectj.weaver.tools.WeavingAdaptor$1@17e3b98]) and a value of type
> [java.lang.Boolean] (value [false]) but failed to remove it when the web
> application was stopped. This is very likely to create a memory leak.
>
> error on Tomcat, when restarting application and I think this is referring
> to the ThreadLocal field
> declared in  org.aspectj.weaver.tools.WeavingAdaptor.java line 287 on
> AspectJ 1.7.0.
>
> Is there any workaround to avoid this leak?
>
>
> Best regards,
> Glenn Marintes
> gmarintes@xxxxxxxxx
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev