maven - Build Best Practices to avoid Classloader leaks - OutOfMemoryError: PermGen space -
i reading post around here outofmemoryerror: permgen space. 1 here took special attention. dealing "java.lang.outofmemoryerror: permgen space" error
also, same post mentions other web references
- http://frankkieviet.blogspot.ca/2006/10/classloader-leaks-dreaded-permgen-space.html http://frankkieviet.blogspot.ca/2006/10/how-to-fix-dreaded-permgen-space.html
as far understood classloader leak is, in cases, associated deployment have classes present inside app classloader beeing referenced outside app classloader. links in posts illustrates example, custom log level.
said that, doubt best practice builds , dependency management. use maven , bill of materials dependency analysis check if not generate package more need. far, good. know there precedence of class loader. in case use jboss / wildfly uses unifiedclassloader.
in case should take in consideration war file built maven , bom may have same behavior example of logger? still recommended use bom?
Comments
Post a Comment