-
Bug
-
Resolution: Fixed
-
P4
-
22, 23
-
b21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8331857 | 22.0.2 | Christoph Langer | P4 | Resolved | Fixed | b06 |
| JDK-8331357 | 21.0.5-oracle | Shivangi Gupta | P4 | Resolved | Fixed | b01 |
| JDK-8331991 | 21.0.4 | Christoph Langer | P4 | Resolved | Fixed | b03 |
| JDK-8332379 | 17.0.12 | Christoph Langer | P4 | Resolved | Fixed | b04 |
| JDK-8337996 | 11.0.25 | Christoph Langer | P4 | Resolved | Fixed | b03 |
It tests a matrix of HTTP client settings and server behavior, resulting in 160 individual test scenarios. Each is tested in an own freshly spawned JVM via the @run main/othervm directive. The need for new VMs is due to the fact that the behavior of the HTTP client is determined at VM initialization and can not be changed later on. However, for each distinct type of client settings, one VM can be reused. This would lead us from 160 JVM instantiations down to 16 which has a factor 10 influence on test runtime.
Furthermore, there is room for additional cleanup in the test.
- backported by
-
JDK-8331357 Reduce runtime and improve efficiency of KeepAliveTest
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/98038b3d
-
Commit
openjdk/jdk21u-dev/c12dfc35
-
Commit
openjdk/jdk22u/8eac95ec
-
Commit
openjdk/jdk/16c7dcdb
-
Commit(master)
openjdk/jdk11u-dev/648e8f01
-
Review
openjdk/jdk17u-dev/2463
-
Review
openjdk/jdk21u-dev/558
-
Review
openjdk/jdk22u/177
-
Review
openjdk/jdk/18817
-
Review(master)
openjdk/jdk11u-dev/2888