You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "John Wagenleitner (JIRA)" <ji...@apache.org> on 2016/01/24 16:14:39 UTC
[jira] [Resolved] (GROOVY-4698) Possible memory leak in Tomcat
[ https://issues.apache.org/jira/browse/GROOVY-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Wagenleitner resolved GROOVY-4698.
---------------------------------------
Resolution: Fixed
Assignee: John Wagenleitner
Fix Version/s: 2.4.6
> Possible memory leak in Tomcat
> ------------------------------
>
> Key: GROOVY-4698
> URL: https://issues.apache.org/jira/browse/GROOVY-4698
> Project: Groovy
> Issue Type: Bug
> Components: groovy-runtime
> Affects Versions: 1.7.8
> Environment: Groovy 1.7.8, Tomcat 6.0.28
> Reporter: François-Xavier Guillemette
> Assignee: John Wagenleitner
> Fix For: 2.4.6
>
>
> Using Groovy 1.7.8 Groovlets on Tomcat 6.0.28 yields the following in the log files:
> {code}
> The web application [...] created a ThreadLocal with key of type [null] (value [groovy.util.GroovyScriptEngine$2@68aed52c]) and a value of type [org.codehaus.groovy.tools.gse.StringSetMap] (value [{}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)