Skip to content
New issue

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

Diagnose "known offenders" on console #22

Open
gusehr opened this issue Sep 15, 2014 · 3 comments
Open

Diagnose "known offenders" on console #22

gusehr opened this issue Sep 15, 2014 · 3 comments

Comments

@gusehr
Copy link

gusehr commented Sep 15, 2014

Hello @mjiderhamn !

What do you think about a diagnosis system that could show some alerts on console about the use of a library version which is known for create a classloader leak?

Thanks in advance.

@mjiderhamn
Copy link
Owner

Do you mean like more informative logging for the existing leak preventor listener, or are you talking about some standalone tool or Maven plugin to analyze your application while it is not running?

@gusehr
Copy link
Author

gusehr commented Sep 15, 2014

I mean about an informative log.
It could be done at the contextInitialized method.

@gusehr
Copy link
Author

gusehr commented Sep 17, 2014

Hello @mjiderhamn .

E.g. the commons-*-1.0.1 have a known leak.
If the library is inside my ".war" file, I can update it, test and deploy.
If the library is provided by the application server, I can take other ways to fix the issue.

What do you think about it?

Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants