-
Bug
-
Resolution: Fixed
-
P4
-
7, 8, 9
-
b10
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8328156 | 17.0.12-oracle | Md Shahbaz Yusuf | P4 | Resolved | Fixed | b01 |
JDK-8330897 | 17.0.12 | Amos SHI | P4 | Resolved | Fixed | b01 |
JDK-8328239 | 11.0.24-oracle | Md Shahbaz Yusuf | P4 | Resolved | Fixed | b01 |
JDK-8330889 | 11.0.24 | Amos SHI | P4 | Resolved | Fixed | b01 |
JDK-8328240 | 8u421 | Md Shahbaz Yusuf | P4 | Resolved | Fixed | b01 |
Those failures are more like the connection failures fixed in similar tests (e.g. JDK-8227337), where:
java.rmi.NoSuchObjectException: no such object in table
..is reported, a startup issue, before the notification work, a failure to connect:
at java.management/javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at NotifReconnectDeadlockTest.main(NotifReconnectDeadlockTest.java:88)
We should do something similar here, but not such that it affects the deadlock timing.
- backported by
-
JDK-8328156 javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java update
- Resolved
-
JDK-8328239 javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java update
- Resolved
-
JDK-8328240 javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java update
- Resolved
-
JDK-8330889 javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java update
- Resolved
-
JDK-8330897 javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java update
- Resolved
- relates to
-
JDK-8327136 javax/management/remote/mandatory/notif/NotifReconnectDeadlockTest.java fails on libgraal
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/7491ed45
-
Commit openjdk/jdk17u-dev/99126663
-
Commit openjdk/jdk/1c7b09bc
-
Review openjdk/jdk11u-dev/2651
-
Review openjdk/jdk17u-dev/2399
-
Review openjdk/jdk/12472