Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 159 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 471 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
JVisualVM hangs when saving threaddumps (at least for large numbers of threads)

I've used VisualVM/JVisualVM for years but as long as I have been using it, it has every time and in every version frozen when I asked it to create a threaddump, specifically in the reload of the threaddump file that it created. I don't think it is the saving of the threaddump that is the problem. Because I can usually kill the VisualVM process (after the prerequisite (hope springs eternal) wait to see if the UI will unfreeze) and when reopening the VisualVM the threaddump does appear under the process node in the left panel. Trying to open that file will rehang VisualVM. But I can "Save As" to disk and load them near instantly in other ThreadDump analyzer tools.
I've tried upping the mem settings etc for Visual VM without success.
Typically this problem only starts to happen when the number of threads in the process (usually tomcat or tcserver) is in the 1000's plus. But just now it happened with a meager 900. With much smaller number of threads it has worked perfectly for me in the past.
When this does happen, not only does the VisualVM fail to respond, but the process is consuming 1 CPU at 100%.
I really like this tool and it would be great if this feature worked reliably.
Thanks