Quantcast

Memory leak?

classic Classic list List threaded Threaded
4 messages Options
mcf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Memory leak?

mcf
I've a grails 2.0.3 application that almost everytime I stop Tomcat there is a catalina.out message like the following....

SEVERE: The web application [] created a ThreadLocal with key of type [org.codehaus.groovy.grails.orm.hibernate.support.HibernatePersistenceContextInterceptor$2] (value [org.codehaus.groovy.grails.orm.hibernate.support.HibernatePersistenceContextInterceptor$2@439ed348]) 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.

What can be done to prevent it?


----
Marcelo Carvalho Fernandes
+55 21 8272-7970

mcf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Memory leak?

mcf
...and also this one...

SEVERE: The web application [/xilya-0.1] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.

----
Marcelo Carvalho Fernandes
+55 21 8272-7970



On Tue, Jun 5, 2012 at 10:16 PM, Marcelo Carvalho Fernandes <[hidden email]> wrote:
I've a grails 2.0.3 application that almost everytime I stop Tomcat there is a catalina.out message like the following....

SEVERE: The web application [] created a ThreadLocal with key of type [org.codehaus.groovy.grails.orm.hibernate.support.HibernatePersistenceContextInterceptor$2] (value [org.codehaus.groovy.grails.orm.hibernate.support.HibernatePersistenceContextInterceptor$2@439ed348]) 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.

What can be done to prevent it?


----
Marcelo Carvalho Fernandes
<a href="tel:%2B55%2021%208272-7970" value="+552182727970" target="_blank">+55 21 8272-7970


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Memory leak?

John Moore
It's not an answer as such, but I just wanted to point out that I've often seen this myself and in my experience it hasn't turned out to be a real problem, just an artefact of the shutdown process. Any apparent memory leaks seem to be sorted by the time I restart Tomcat.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Memory leak?

ACMattos
In reply to this post by mcf
Hi Marcelo,

I´ve already seen this kind of problem since Grails 1.3.7. As I can
see it´s still there, unfortunately.


Cheers,

ACMattos.

On 6/5/12, Marcelo Carvalho Fernandes <[hidden email]> wrote:

> ...and also this one...
>
> SEVERE: The web application [/xilya-0.1] appears to have started a thread
> named [Timer-1] but has failed to stop it. This is very likely to create a
> memory leak.
>
> ----
> Marcelo Carvalho Fernandes
> +55 21 8272-7970
>
>
>
> On Tue, Jun 5, 2012 at 10:16 PM, Marcelo Carvalho Fernandes <
> [hidden email]> wrote:
>
>> I've a grails 2.0.3 application that almost everytime I stop Tomcat there
>> is a catalina.out message like the following....
>>
>> SEVERE: The web application [] created a ThreadLocal with key of type
>> [org.codehaus.groovy.grails.orm.hibernate.support.HibernatePersistenceContextInterceptor$2]
>> (value
>> [org.codehaus.groovy.grails.orm.hibernate.support.HibernatePersistenceContextInterceptor$2@439ed348])
>> 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.
>>
>> What can be done to prevent it?
>>
>>
>> ----
>> Marcelo Carvalho Fernandes
>> +55 21 8272-7970
>>
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Loading...