jstack mixed mode and jhsdb stack mixed mode can not get expected result(stack trace is incomplete) on latest ubuntu or fedora or RHEL 8 beta

Sharath Ballal sharath.ballal at oracle.com
Fri Feb 15 09:45:34 UTC 2019


Hi Gao,

 

I also observed this failure and opened HYPERLINK "https://bugs.openjdk.java.net/browse/JDK-8219086"JDK-8219086 for it.

 

 

Thanks,

Sharath

 

 

From: Shuai Gao 
Sent: Friday, February 15, 2019 12:15 PM
To: serviceability-dev at openjdk.java.net
Subject: jstack mixed mode and jhsdb stack mixed mode can not get expected result(stack trace is incomplete) on latest ubuntu or fedora or RHEL 8 beta

 

Hello,

 

I tried “jstack -m PID”in latest openjdk 8 64-bit and “jhsdb jstack –mixed –pid PID” in latest openjdk 11 64-bit on latest Ubuntu(18.04) and latest fedora (29) and RHEL 8 Beta.

The stack traces returned are always incomplete like following output:

 

----------------- 1479 -----------------

"DestroyJavaVM" #17 prio=5 tid=0x0000000000bae000 nid=0x5c7 waiting on condition [0x0000000000000000]

   java.lang.Thread.State: RUNNABLE

   JavaThread state: _thread_blocked

0x00007f839224f9f3  __pthread_cond_wait + 0x243

----------------- 1480 -----------------

----------------- 1481 -----------------

"Reference Handler" #2 daemon prio=10 tid=0x0000000000c36000 nid=0x5c9 waiting on condition [0x00007f8376d15000]

   java.lang.Thread.State: RUNNABLE

   JavaThread state: _thread_blocked

0x00007f839224f9f3  __pthread_cond_wait + 0x243

----------------- 1482 -----------------

"Finalizer" #3 daemon prio=8 tid=0x0000000000c3a000 nid=0x5ca in Object.wait() [0x00007f8376c14000]

   java.lang.Thread.State: WAITING (on object monitor)

   JavaThread state: _thread_blocked

0x00007f839224f9f3  __pthread_cond_wait + 0x243

----------------- 1483 -----------------

"Signal Dispatcher" #4 daemon prio=9 tid=0x0000000000c56800 nid=0x5cb runnable [0x0000000000000000]

   java.lang.Thread.State: RUNNABLE

   JavaThread state: _thread_blocked

0x00007f83922526d6  do_futex_wait.constprop.1 + 0x36

 

The issue existed even after I disable the selinux. It can not be reproduced on oracle linux 7.4.

The kernel version on Ubuntu or fedora is 4.15. the kernel version on RHEL 8 Beta is 4.18. the kernel version on Oracle linux 7.4 is 3.1.

I can not find any existed bug for now.

 

 

Is there any clue about this issue?

 

Any reply will be appreciated.

 

Best Regards

Gao Shuai from GCS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20190215/a1e10526/attachment.html>


More information about the serviceability-dev mailing list