Can you open a jira issue with this information so that it doesn't get
forgotten. I'd like to see a solution, just don't have the time to
tackle it myself at the moment.
2010/9/23 Pablo Graña :
> Here is more info on the problem and the current status:
>
> http://code.google.com/p/guava-librarie
I created ticket https://issues.apache.org/jira/browse/SHINDIG-1439
for the shutdown hook.
I read a little bit more about thread locals, and I think that caching
the DocumentBuilder in a ThreadLocal should not create a memory leak.
See this blog post:
http://blog.crazybob.org/2006/07/hard-core-jav
Here is more info on the problem and the current status:
http://code.google.com/p/guava-libraries/issues/detail?id=92
Guys from guice copied the classes from guava (or google-collections),
bringing the same problem to guice.
The memory leaks manifests with hot redeploys in tomcat, after a couple
Hi Pablo
I couldn't understand the memory leak you found in Guice. Hopefully crazy
bob will fix it soon (it has been 3 months already).
As for the shindig shutdown hook, it looks like an innocent hook which tries
to stop the executor service which is where all the threads are scheduled.
Did you fi
Hi guys.
I get an oom after some hot deploys. I traced one problem to Guice (
http://www.mail-archive.com/google-gu...@googlegroups.com/msg02987.html -
there is a workaround) and another to shindig: the DefaultGuiceModule
installs a shutdown hook, apparently with the idea to shut down a thread
poo
