Creating thread dump via JMX console is slower than with jstack or kill -3

Solution Verified - Updated -

Issue

  • I created a thread dump using JMX-console, and it took a very long time (~1 minute), and in the gc log there are many application-stopped-times with 4 seconds each.

  • Right after that I made a kill -3 to create another thread dump with no impact on the JVM.

Environment

  • JBoss Enterprise Application Platform (EAP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.