ADDITIONAL SYSTEM INFORMATION :
Version: 1.8.0_152 (Build 1390-170114); platform 20170114-unknown-revn
System: Windows 7 (6.1) Service Pack 1, amd64 64bit
Java: 1.8.0_152; Java HotSpot(TM) 64-Bit Server VM (25.152-b16, mixed mode)


A DESCRIPTION OF THE PROBLEM :
When a remote process is connected to JVisualVM via JMX and this remote process has - by incident - the same process ID as one of the already existing local Java processes (subject to monitoring), JVisualVM is unable to display the monitoring details of this process. Instead, the details of the local process are shown (again).

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
- File / Add JMX Connection / enter connection details
- New JMX connection is added to the "Local" process tree
- The JMX connection refers to a remote process ID which is - by incident - equal to one of the local process IDs listed further above
- Once you click "open" the monitoring details of the local process are displayed instead of the remote process

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The monitoring details of the remote proccess (connected via JMX) are displayed.
ACTUAL -
The monitoring details of the local proccess which - by incident - has the same PID as the remote process are displayed.

FREQUENCY : always