Describe the bug
I used to have an IP of 10.30.90.39. I added my containerized Java instance to the list of remote instances to collect a HeapDump. The DHCP makes IPs rotate. A month ago it got changed to 10.30.90.109. Now VisualVM fails to start because it tries for some reason to open a connection 10.30.90.39 on startup. The first thing you learn when writing network code, is that nothing can be guaranteed to you, including having a single IP for the lifetime of a computer. The install is also a clean download from https://github.com/oracle/visualvm/releases/download/2.2.1/visualvm_221.zip.
Deleting $HOME/.visualvm solves the issue.
Expected behavior
Application should launch without trying to unconditionally open a connection to an unreachable host and crash.
VisualVM log
log.log
Desktop (please complete the following information):
- OS: 24.04.4 LTS (Noble Numbat)
- JDK version: openjdk 25.0.3 2026-04-21
- Version: 2.2.1
Additional context
Running with JAVA_HOME set to JDK 8, 11, 25 does not work either.
Describe the bug
I used to have an IP of
10.30.90.39. I added my containerized Java instance to the list of remote instances to collect a HeapDump. The DHCP makes IPs rotate. A month ago it got changed to10.30.90.109. Now VisualVM fails to start because it tries for some reason to open a connection10.30.90.39on startup. The first thing you learn when writing network code, is that nothing can be guaranteed to you, including having a single IP for the lifetime of a computer. The install is also a clean download fromhttps://github.com/oracle/visualvm/releases/download/2.2.1/visualvm_221.zip.Deleting
$HOME/.visualvmsolves the issue.Expected behavior
Application should launch without trying to unconditionally open a connection to an unreachable host and crash.
VisualVM log
log.log
Desktop (please complete the following information):
Additional context
Running with JAVA_HOME set to JDK 8, 11, 25 does not work either.