io.openliberty.transport.http_fat.MaxMessageSizeLimitTests.testBoundary_greaterThan_2GB_Chunk_IsRejected intermittently fails with:
java.net.ConnectException: Connection refused
at io.openliberty.transport.http_fat.MaxMessageSizeLimitTests
.testBoundary_greaterThan_2GB_Chunk_IsRejected(MaxMessageSizeLimitTests.java:349)
The failure occurs before the test sends the chunk-size request. It is therefore not an assertion failure in the 2GB-overflow rejection behavior.
The preceding test deliberately sends a huge chunk-size header, waits for a read timeout, then closes its socket without providing the declared body. This causes a race condition with this test's cleanup and the subsequent testBoundary_greaterThan_2GB_Chunk_IsRejected test.
The preceding test abruptly abandons a live server-side socket read, and recycles the TCP channel before that server-side cleanup finishes, leaving a brief window where the next test's new Socket() lands on a closed port that causes the test to fail with Connection refused.
io.openliberty.transport.http_fat.MaxMessageSizeLimitTests.testBoundary_greaterThan_2GB_Chunk_IsRejected intermittently fails with:
java.net.ConnectException: Connection refused
at io.openliberty.transport.http_fat.MaxMessageSizeLimitTests
.testBoundary_greaterThan_2GB_Chunk_IsRejected(MaxMessageSizeLimitTests.java:349)
The failure occurs before the test sends the chunk-size request. It is therefore not an assertion failure in the 2GB-overflow rejection behavior.
The preceding test deliberately sends a huge chunk-size header, waits for a read timeout, then closes its socket without providing the declared body. This causes a race condition with this test's cleanup and the subsequent testBoundary_greaterThan_2GB_Chunk_IsRejected test.
The preceding test abruptly abandons a live server-side socket read, and recycles the TCP channel before that server-side cleanup finishes, leaving a brief window where the next test's new Socket() lands on a closed port that causes the test to fail with Connection refused.