-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 18
-
b26
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8280156 | 17.0.3-oracle | Vaibhav Choudhary | P4 | Resolved | Fixed | b03 |
| JDK-8280570 | 17.0.3 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
https://github.com/openjdk/jdk/pull/5231#pullrequestreview-784995993
I think this is an existing bug. Do we need this catch block? TouchedMethodsDCmd is always enabled as long as the current JVM has INCLUDE_SERVICES is true. If INCLUDE_SERVICES is false, the jcmd connection will fail, and you will get a different error, like
`com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file /proc/18810/root/tmp/.java_pid18810: target process 18810 doesn't respond within 10500ms or HotSpot VM not loaded`
The catch block will incorrectly ignore the problem if the VM is incorrectly modified and the TouchedMethodsDCmd is inadvently excluded.
I think this is an existing bug. Do we need this catch block? TouchedMethodsDCmd is always enabled as long as the current JVM has INCLUDE_SERVICES is true. If INCLUDE_SERVICES is false, the jcmd connection will fail, and you will get a different error, like
`com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file /proc/18810/root/tmp/.java_pid18810: target process 18810 doesn't respond within 10500ms or HotSpot VM not loaded`
The catch block will incorrectly ignore the problem if the VM is incorrectly modified and the TouchedMethodsDCmd is inadvently excluded.
- backported by
-
JDK-8280156 runtime/CommandLine/PrintTouchedMethods test shouldn't catch RuntimeException
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/6315ce3c
-
Commit
openjdk/jdk/f0136ec9
-
Review
openjdk/jdk17u-dev/115
-
Review
openjdk/jdk/6536
(1 links to)