Websphere 6.1 (IBM JVM) 中的类加载器地址怎么会发生变化
我在连续的 javacore 转储中观察到类加载器的地址在 Websphere 6.1 (IBM JVM 1.5.0) 中发生了变化。 类加载器下面的类的地址没有变化。 那么新地址不是同一个类加载器吗？
例如在第一个javacore中
2CLTEXTCLLOAD 加载器 com/ibm/ws/classloader/CompoundClassLoader(0x00002AAABF5BB7F0)
3CLTEXTCLASS org/eclipse/emf/ecore/EObject(0x00002AAB24684B30)
以及更高版本的 javacore
2CLTEXTCLLOAD 加载程序 com/ibm/ws/classloader/CompoundClassLoader(0x00002AAABF5AB6E0)
3CLTEXTCLASS org/eclipse/emf/ecore/EObject(0x00002AAB24684B30)
以前在类加载器下的同一个类位于 0x00002AAABF5BB7F0，现在类加载器位于 0x00002AAABF5AB6E0
我正在尝试找出类卸载问题，但这似乎并没有让生活变得更轻松当挖掘堆转储时。
I observe in consecutive javacore dumps that the addresses of classloaders are changing in Websphere 6.1 (IBM JVM 1.5.0). The classes below the classloader have unchanged address. So isn't it the same classloader at a new address?
E.g. in first javacore
2CLTEXTCLLOAD Loader com/ibm/ws/classloader/CompoundClassLoader(0x00002AAABF5BB7F0)
3CLTEXTCLASS org/eclipse/emf/ecore/EObject(0x00002AAB24684B30)
and in a later javacore
2CLTEXTCLLOAD Loader com/ibm/ws/classloader/CompoundClassLoader(0x00002AAABF5AB6E0)
3CLTEXTCLASS org/eclipse/emf/ecore/EObject(0x00002AAB24684B30)
Same class previously under a classloader at 0x00002AAABF5BB7F0, and now the classloader is at 0x00002AAABF5AB6E0
I'm trying to figure out a class unloading problem, and this does not seem to make life easier when digging through heap dumps.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
也许 GC 正在压缩堆。 将 -Xnocompactgc 或 -Xnocompactexplicitgc 视为通用 JVM 参数。 请参阅 IBM JDK 诊断文档：
http://www.ibm.com/developerworks/java/jdk/diagnosis/< /a>
Perhaps the GC is compacting the heap. Consider -Xnocompactgc or -Xnocompactexplicitgc as a generic JVM arguments. See IBM JDK diagnoses documentation:
http://www.ibm.com/developerworks/java/jdk/diagnosis/
如果应用程序停止并重新启动，是否会因为存在应用程序类加载器而为您的类创建新的类加载器？
您是否因为本机堆消耗或其他原因而担心这个问题？
If the application was stopped and restarted wouldnt' new classloaders be created for your classes because there is an application classloader?
Are you concerned about this because of native heap consumption or something else?