-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b01
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8313328 | 8u401 | Abhishek N | P4 | Resolved | Fixed | b01 |
While investigating improvement fix for 7144861 Rmi activation tests are too slow,
It has been noticed that all the activation, ang more generally speaking all the rmi
regression tests would need some cleanup in the future.
As an example, but not limited to, the rmi/testlibrary classes, as well as some other
rmi tests (activation or not) do use timer loops with Thread.sleep() blocking method(),
for which InterruptedException is not handled at all.
At least reasonable cleanup would be largely beneficial to the whole set of rmi regression tests
It has been noticed that all the activation, ang more generally speaking all the rmi
regression tests would need some cleanup in the future.
As an example, but not limited to, the rmi/testlibrary classes, as well as some other
rmi tests (activation or not) do use timer loops with Thread.sleep() blocking method(),
for which InterruptedException is not handled at all.
At least reasonable cleanup would be largely beneficial to the whole set of rmi regression tests
- backported by
-
JDK-8313328 TEST_BUG: Cleanup of rmi regression tests (activation and others)
-
- Resolved
-
- relates to
-
JDK-8005436 TEST_BUG: speed up RMI tests
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-