-
Bug
-
Resolution: Fixed
-
P4
-
9
-
b134
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8313863 | 8u401 | kiran kumar J | P4 | Resolved | Fixed | b01 |
The following tests may leave daemon threads after they finished:
java/nio/channels/AsynchronousSocketChannel/Leaky.java
java/nio/channels/AsynchronousChannelGroup/Identity.java
The tests above use AsynchronousChannelGroup.withFixedThreadPool() to create instances of AsynchronousChannelGroup. Leaky.java test doesn't shutdown AsynchronousChannelGroup. Identity.java test uses shutdownNow() method, but this method is not called in "finally" block, so that it may be possible that the test leaves daemon threads.
The tests shouldn't leave daemon threads when they finishes. It may slow down further test execution. If other tests also leave daemon threads, it may cause intermittent test failures, see for exampleJDK-8160642 and JDK-8162757.
java/nio/channels/AsynchronousSocketChannel/Leaky.java
java/nio/channels/AsynchronousChannelGroup/Identity.java
The tests above use AsynchronousChannelGroup.withFixedThreadPool() to create instances of AsynchronousChannelGroup. Leaky.java test doesn't shutdown AsynchronousChannelGroup. Identity.java test uses shutdownNow() method, but this method is not called in "finally" block, so that it may be possible that the test leaves daemon threads.
The tests shouldn't leave daemon threads when they finishes. It may slow down further test execution. If other tests also leave daemon threads, it may cause intermittent test failures, see for example
- backported by
-
JDK-8313863 Make sure java/nio/channels tests shutdown asynchronous channel groups
-
- Resolved
-
- relates to
-
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-