-
Bug
-
Resolution: Fixed
-
P2
-
6
As of Mustang b73 JConsole lost the ability to reconnect an established window to a remote VM that has been restarted on the same port. This may be the desired behavior, since it is difficult to verify that all the resources of the remote mbeans will match the previously collected data.
There are however some user experience issues involved here. I would think that if during a retry attempt we detect that a new VM has been started on the same port as the old, then we ought to either automatically create a new window (using a new ProxyClient instance), or at least inform the user about this and either offer to create the new window or suggest that it is done manually.
The most serious issue is that it is currently impossible to create a new window in order to make a new connection to the restarted VM.
There are however some user experience issues involved here. I would think that if during a retry attempt we detect that a new VM has been started on the same port as the old, then we ought to either automatically create a new window (using a new ProxyClient instance), or at least inform the user about this and either offer to create the new window or suggest that it is done manually.
The most serious issue is that it is currently impossible to create a new window in order to make a new connection to the restarted VM.
- relates to
-
JDK-6387250 Regression: JConsole fails to connect to a JMX agent of a given JMXServiceURL
-
- Resolved
-
-
JDK-6361632 Ability to connect to JMX agent with SSL/TLS-protected RMI registry
-
- Resolved
-