-
Bug
-
Resolution: Fixed
-
P3
-
5.0
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8018821 | 7u45 | Nils Loodin | P3 | Closed | Fixed | b01 |
| JDK-8015488 | 7u40 | Nils Loodin | P3 | Closed | Fixed | b28 |
Connect to a JMX Agent
Click on disconnect button
A popup is displayed with a message saying that the connection with the remote process has been lost... This is not what happened. The process is not dead, the client disconnected explicitely from the agent. Further more, in order to go back to disconnected JConsole, a user need to click Cancel. If OK is pressed, the Connection is reestablished.
This connection feature seems broken.
What should be expected is :
1 Nothing. Just let the user disconnect because he wants to do it.
2 Or display a popup dialog to confirm that you want to disconnect. If OK is pressed, the connection is disconnected, if cancel is pressed, nothing is Done.
It seems that this behavior has bee nintroduced in Beta 2, it used to be behavior 1 in beta release.
Click on disconnect button
A popup is displayed with a message saying that the connection with the remote process has been lost... This is not what happened. The process is not dead, the client disconnected explicitely from the agent. Further more, in order to go back to disconnected JConsole, a user need to click Cancel. If OK is pressed, the Connection is reestablished.
This connection feature seems broken.
What should be expected is :
1 Nothing. Just let the user disconnect because he wants to do it.
2 Or display a popup dialog to confirm that you want to disconnect. If OK is pressed, the connection is disconnected, if cancel is pressed, nothing is Done.
It seems that this behavior has bee nintroduced in Beta 2, it used to be behavior 1 in beta release.
- backported by
-
JDK-8015488 Disconnect button leads to wrong popup message
-
- Closed
-
-
-
- Closed
-