-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b43
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084730 | emb-9 | Stuart Marks | P3 | Resolved | Fixed | team |
javax/management/remote/mandatory/connection/RMIConnector_NPETest.java fails on all platforms:
JavaTest Message: Test threw exception: TestFailedException: TEST FAILED: Failed to start rmid, giving up after 159ms.
The reason is that it calls RMID.start() using a timeout period of Long.MAX_VALUE, which causes the deadline timestamp to overflow and wrap around to negative. As a result, the first check against the timestamp seems to indicate a timeout and so the test fails.
JavaTest Message: Test threw exception: TestFailedException: TEST FAILED: Failed to start rmid, giving up after 159ms.
The reason is that it calls RMID.start() using a timeout period of Long.MAX_VALUE, which causes the deadline timestamp to overflow and wrap around to negative. As a result, the first check against the timestamp seems to indicate a timeout and so the test fails.
- backported by
-
JDK-8084730 TEST_BUG: javax/management/remote/mandatory/connection/RMIConnector_NPETest.java fails
-
- Resolved
-
- relates to
-
JDK-8067316 TEST_BUG: update RMI test library with better test.timeout.factor handling
-
- Resolved
-