-
Bug
-
Resolution: Fixed
-
P4
-
11, 16
-
b11
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8271267 | 11.0.13-oracle | Ravi Reddy | P4 | Resolved | Fixed | b04 |
JDK-8272416 | 11.0.13 | Aleksey Shipilev | P4 | Resolved | Fixed | b03 |
The issue was reported on the net-dev mailing list:
https://mail.openjdk.java.net/pipermail/net-dev/2020-July/014191.html
There is a subtle timing hole introduced into the HttpURLConWithProxy.java test with the fix forJDK-8183369.
When using GC stress modes, a consistent failure can be observed:
"Execution failed: `main' threw exception: java.lang.RuntimeException: Connection not retried with proxy".
It can be verified that the Proxy is being used but the messages are not being logged with the ProxyHandler. The issue is caused by back to back calls of Logger.getLogger(String). If a GC happens between the two calls
there is no guarantee that the same object will be returned.
Since the test relies on the log messages being handled by the new ProxyHandler to pass, the test needs to ensure the Logger object stays live for the entire lifetime of the test.
https://mail.openjdk.java.net/pipermail/net-dev/2020-July/014191.html
There is a subtle timing hole introduced into the HttpURLConWithProxy.java test with the fix for
When using GC stress modes, a consistent failure can be observed:
"Execution failed: `main' threw exception: java.lang.RuntimeException: Connection not retried with proxy".
It can be verified that the Proxy is being used but the messages are not being logged with the ProxyHandler. The issue is caused by back to back calls of Logger.getLogger(String). If a GC happens between the two calls
there is no guarantee that the same object will be returned.
Since the test relies on the log messages being handled by the new ProxyHandler to pass, the test needs to ensure the Logger object stays live for the entire lifetime of the test.
- backported by
-
JDK-8271267 Potential race between Logger configuration and GCs in HttpURLConWithProxy test
- Resolved
-
JDK-8272416 Potential race between Logger configuration and GCs in HttpURLConWithProxy test
- Resolved
- relates to
-
JDK-8183369 RFC unconformity of HttpURLConnection with proxy
- Closed