-
Bug
-
Resolution: Fixed
-
P4
-
19
-
b09
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8297825 | 17.0.7-oracle | Dukebot | P4 | Resolved | Fixed | b01 |
JDK-8299581 | 17.0.7 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
The LineBodyHandlerTest.java creates and discards many clients (64).
The test has been observed failing intermittently on some systems (Windows 10) while trying to open the client's selector, apparently due to some connection limit (see below).
It seems that using a single client reduces the occurrences in which the test fails.
java.io.IOException: Unable to establish loopback connection
at java.base/sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:99)
at java.base/sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:65)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
at java.base/sun.nio.ch.PipeImpl.<init>(PipeImpl.java:188)
at java.base/sun.nio.ch.WEPollSelectorImpl.<init>(WEPollSelectorImpl.java:78)
at java.base/sun.nio.ch.WEPollSelectorProvider.openSelector(WEPollSelectorProvider.java:33)
at java.base/java.nio.channels.Selector.open(Selector.java:295)
at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.<init>(HttpClientImpl.java:719)
at java.net.http/jdk.internal.net.http.HttpClientImpl.<init>(HttpClientImpl.java:323)
... 33 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:579)
at java.base/sun.nio.ch.Net.connect(Net.java:586)
at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:853)
at java.base/java.nio.channels.SocketChannel.open(SocketChannel.java:285)
at java.base/sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(PipeImpl.java:129)
at java.base/sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:81)
The test has been observed failing intermittently on some systems (Windows 10) while trying to open the client's selector, apparently due to some connection limit (see below).
It seems that using a single client reduces the occurrences in which the test fails.
java.io.IOException: Unable to establish loopback connection
at java.base/sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:99)
at java.base/sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:65)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
at java.base/sun.nio.ch.PipeImpl.<init>(PipeImpl.java:188)
at java.base/sun.nio.ch.WEPollSelectorImpl.<init>(WEPollSelectorImpl.java:78)
at java.base/sun.nio.ch.WEPollSelectorProvider.openSelector(WEPollSelectorProvider.java:33)
at java.base/java.nio.channels.Selector.open(Selector.java:295)
at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.<init>(HttpClientImpl.java:719)
at java.net.http/jdk.internal.net.http.HttpClientImpl.<init>(HttpClientImpl.java:323)
... 33 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:579)
at java.base/sun.nio.ch.Net.connect(Net.java:586)
at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:853)
at java.base/java.nio.channels.SocketChannel.open(SocketChannel.java:285)
at java.base/sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(PipeImpl.java:129)
at java.base/sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:81)
- backported by
-
JDK-8297825 LineBodyHandlerTest.java creates and discards too many clients
- Resolved
-
JDK-8299581 LineBodyHandlerTest.java creates and discards too many clients
- Resolved
- relates to
-
JDK-8280944 Enable Unix domain sockets in Windows Selector notification mechanism
- Resolved
- links to
-
Commit openjdk/jdk17u-dev/26f03487
-
Commit openjdk/jdk/47800bf3
-
Review openjdk/jdk17u-dev/1019
-
Review openjdk/jdk/7263
(2 links to)