jhsdb jstack does not work with AppCDS (original) (raw)

Yasumasa Suenaga yasuenag at gmail.com
Mon Mar 26 04:08:40 UTC 2018

Thanks Jini,

I will watch JDK-8174994.

Yasumasa

On 2018/03/26 10:39, Jini George wrote:

Hi Yasumasa,

This is likely to be due to JDK-8174994 (for which I am working on a fix right now, and which I hope to send for review in a day or two). Thank you, Jini.

On 3/25/2018 6:46 PM, Yasumasa Suenaga wrote: Hi all,

I tried to get jstack via jhsdb from AppCDS enabled process, but it couldn't as below: --------------- [ysuenaga at fc27 jdk-hs]$ /usr/local/jdk-10/bin/jhsdb jstack --pid 5614 Attaching to process ID 5614, please wait... Debugger attached successfully. Server compiler detected. JVM version is 10+46 Deadlock Detection: sun.jvm.hotspot.types.WrongTypeException: No suitable match for type of address 0x0000000800098690 ??????? at jdk.hotspot.agent/sun.jvm.hotspot.runtime.InstanceConstructor.newWrongTypeException(InstanceConstructor.java:62) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.runtime.VirtualBaseConstructor.instantiateWrapperFor(VirtualBaseConstructor.java:109) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.oops.Metadata.instantiateWrapperFor(Metadata.java:73) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.oops.Oop.getKlassForOopHandle(Oop.java:210) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.oops.ObjectHeap.newOop(ObjectHeap.java:252) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.runtime.JavaThread.getThreadObj(JavaThread.java:359) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.runtime.JavaThread.getCurrentParkBlocker(JavaThread.java:411) ??????? at jdk.hotspot.agent/sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:82) ?--------------- I attempt to change SA to refer Klass::archivedmirror, but I got same exceptions. How can I avoid this error?

Thanks, Yasumasa

More information about the serviceability-dev mailing list