We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From m.zabel.92 on August 28, 2013 07:58:42
When a simple guice servlet application is created, e.g. following the example in the wiki ( https://code.google.com/p/google-guice/wiki/ServletModule ), it can be deployed and redeployed several times without problems.
With the usage of guice-persist a memory leak occurs. This happens as soon as the following two lines are added to the configuration class:
install(new JpaPersistModule("name")); filter("/*").through(PersistFilter.class);
On a running application server (tested with Tomcat) multiple redeploys result in a PermGen exception.
As a profiler reveals, several instances of Guice's own classes cannot be garbage collected after undeployment.
This was tested with guice version 4.0-beta and 3.0.
Original issue: http://code.google.com/p/google-guice/issues/detail?id=768
The text was updated successfully, but these errors were encountered:
From sberlin on December 20, 2013 06:15:49
(No comment was entered for this change.)
Labels: Component-Persist
Sorry, something went wrong.
No branches or pull requests
From m.zabel.92 on August 28, 2013 07:58:42
When a simple guice servlet application is created, e.g. following the example in the wiki ( https://code.google.com/p/google-guice/wiki/ServletModule ), it can be deployed and redeployed several times without problems.
With the usage of guice-persist a memory leak occurs. This happens as soon as the following two lines are added to the configuration class:
install(new JpaPersistModule("name"));
filter("/*").through(PersistFilter.class);
On a running application server (tested with Tomcat) multiple redeploys result in a PermGen exception.
As a profiler reveals, several instances of Guice's own classes cannot be garbage collected after undeployment.
This was tested with guice version 4.0-beta and 3.0.
Original issue: http://code.google.com/p/google-guice/issues/detail?id=768
The text was updated successfully, but these errors were encountered: