I bet you have a permgen leak in your application
summary
Claims class loader leaks appear in almost every app (quoted as 99.9%), and a tiny three‑page app yields five different leaks during debugging. Uses Eclipse MAT and a homegrown tool Plombir to find four reported leaks in a live demo. Fixes include upgrading JDBC drivers, calling DriverManager deregister, closing pooled datasources, avoiding long‑living ThreadLocal entries, setting datasource flags to stop driver registration, or upgrading Java 6→7 to eliminate several root causes.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:17What is a class loader leak
- 2:21Permgen constant generation
- 5:55Why leaks happen
- 9:10PLOMBIR app case
- 10:16First leak found
- 13:41PLOMBIR demo
- 16:11Driver leak fix
- 18:46Detecting the problem
- 21:04Bouncy Castle issue
- 22:35Unclosed resources
- 24:01Resource cleanup rule
- 25:11App restart causes
- 26:28Class loader leak demo
- 28:16Unknown leak cause
- 28:59Java 7 upgrade
- 30:34Why update Java
- 31:42Class loaders and threads
- 32:40JDBC driver leak
- 36:38Manual leak search
- 38:32Automatic leak detection
- 39:13Custom logger issues
- 41:24ThreadLocal misuse
- 43:06JBoss and loggers
- 43:50Five bad Java features
- 45:17ThreadLocal problem
- 45:57Final client report
- 47:54Conclusion and Q&A
related talks
46mPlumbing memory leaks in Java
02h 41mSolving Memory Leaks in the JVM
43mTroubleshooting Memory Problems in Java Applications
26mFind Java memory leaks with Heap Dumps (JDK 25)
38mMemory Efficient Java
45mA Healthy diet for your Java application
51mA Healthy diet for your Java application
56mJava Performance Analysis