Featured White Papers

• Why choose an Open Source BPM?
• 10 FAQs on Business Process Management
• Best Practices for Getting Started with BPM
• Free Your Devs From The Pain Of Java Redeploys
• Increase Velocity 40% by Using JRebel
• What Developers Want: The End of Application Redeploys
• Developer Productivity Report: Java Tools, Tech, Devs, and Data
• Coding with JRebel: Java Forever Changed
• Utilizing Fast Testing to Transform Java Development
• Do You Really Get Classloaders?
• Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
• Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
• Coding with JRebel, Java Forever Changed
• 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data

Sponsored Links

• APIs for Java Programmers: Manage & Convert DOC, XLS, PPT, PDF & More

• Instantly Preview Java Code Changes: JRebel.com

Sponsored Links

Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs

Back to your Class roots, continued

Find runtime origins for <em>all</em> loaded classes

By Vladimir Roubtsov, JavaWorld.com, 07/25/03

Page 3 of 3

Of course, you need to deploy both the modified java.lang.ClassLoader and ClassLoaderRegistry in the JVM's bootstrap classpath (using the -Xbootclasspath/p: JVM option) to make this work. This approach is probably only for dedicated Java hackers.

Finally, if you are willing to forgo pure Java, you can take an entirely different route with the JVM Profiler Interface (JVMPI). Using a JVMPI agent to track classload events is fairly simple to implement. An additional advantage of this approach is the ability to track all classes (bootstrap or otherwise) in the JVM. However, enabling JVMPI places the JVM in an unsuitable mode for production (e.g., it limits the garbage collection modes the JVM can use), so once again you are restricted to testing and debugging.

About the author