Jiri Sedlacek

Automating/scheduling thread/heap dumps is not available out of the box but can be easily achieved using a custom plugin. The following code snippets illustrate how to do it: At first...

Should now be easier to achieve using an external timer calling the new command-line options: #319 & #320.

Can you please specify the VisualVM version you're using?

Thanks for the report! Please verify that using the "--jdkhome" parameter works for you - see the First Steps section at the bottom of http://visualvm.github.io/download.html.

Do you mean you had to use `visualvm.exe --jdkhome C:/Path/To/` instead of `visualvm.exe --jdkhome C:\Path\To\` on Windows? Please provide the full command to start VisualVM on your setup to make...

Tested on a fresh Windows 10 installation, VisualVM 2.0 and AdoptOpenJDK 11.0.6. Using the Windows installer, default settings, the JDK is installed to `C:\Program Files\AdoptOpenJDK\jdk-11.0.6.10-hotspot`, and the Windows registry is...

Using --jdkhome or editing etc/visualvm.conf should have the same effect. Can you please share your command to start VisualVM using the --jdkhome switch and the working visualvm.conf file?

You can define custom name for your profiling configuration, just modify the default settings in Sampler | Settings or Profiler | Settings and click Preset | Custom | Save... at...

Thanks for the bugreport! As a workaround until fixed, you can use VisualVM 1.3.9 and set the 'OQLController.limitResults' system property - like 'visualvm -J-DOQLController.limitResults=200' for up to 200 results etc.

Fixed in master - restored configuring the OQL results limit using the 'OQLController.limitResults' system property. Switching to enhancement and leaving open for further investigation of exporting unlimited results.