search

dschulten / lambdaj

Automatically exported from code.google.com/p/lambdaj
Apache License 2.0
0 stars 0 forks source link

Probable memory leak detected by Tomcat #99

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Whe application using LambdaJ is redeployed, Tomcat writes to the log 
information about probable memory leak

What version of the product are you using? On what operating system?
2.3.3 and 2.4

Please provide any additional information below.

17.7.2012 16:03:28 org.apache.catalina.loader.WebappClassLoader 
checkThreadLocalMapForLeaks
SEVERE: The web application [/XXX] created a ThreadLocal with key of type 
[ch.lambdaj.function.argument.ArgumentsFactory$1] (value 
[ch.lambdaj.function.argument.ArgumentsFactory$1@127fbd60]) and a value of type 
 [ch.lambdaj.function.argument.ArgumentsFactory.LimitedValuesArgumentHolder] 
(value 
[ch.lambdaj.function.argument.ArgumentsFactory$LimitedValuesArgumentHolder@69f31
d]) but failed to remove it when the web application was stopped. Threads are 
going to be renewed over time to try and avoid a probable memory leak.

Original issue reported on code.google.com by bedla.cz...@gmail.com on 15 Aug 2012 at 5:59

GoogleCodeExporter commented 8 years ago 
Created pull request at GitHub https://github.com/mariofusco/lambdaj/pull/1

Original comment by bedla.cz...@gmail.com on 27 Aug 2012 at 6:29

GoogleCodeExporter commented 8 years ago 
I think is very important to fix.

Original comment by a.unterw...@gmail.com on 25 Nov 2013 at 3:43

GoogleCodeExporter commented 8 years ago 
I am also getting the same message on GlassFish 4.0 and 3.1.2.
There is a significant memory leak and after about 2 days running, glassfish 
uses more than 95% of CUP usage and crashes. Please address this issue. Thanks 
in advance.

Original comment by buddhika...@gmail.com on 4 Feb 2014 at 10:33