showuon opened a new pull request, #13031:
URL: https://github.com/apache/kafka/pull/13031

   Saw this flaky test in recent builds: 
[#1452](https://ci-builds.apache.org/job/Kafka/job/kafka/job/trunk/1452/testReport/junit/org.apache.kafka.common.network/SslTransportLayerTest/Build___JDK_17_and_Scala_2_13____3__tlsProtocol_TLSv1_3__useInlinePem_false/),
 
[#1454](https://ci-builds.apache.org/job/Kafka/job/kafka/job/trunk/1454/testReport/junit/org.apache.kafka.common.network/SslTransportLayerTest/Build___JDK_17_and_Scala_2_13____2__tlsProtocol_TLSv1_2__useInlinePem_true/),
 
   ```
   org.opentest4j.AssertionFailedError: Unexpected channel state EXPIRED ==> 
expected: <true> but was: <false>
        at 
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
        at 
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
        at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
        at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
        at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:210)
        at 
app//org.apache.kafka.common.network.SslTransportLayerTest.testIOExceptionsDuringHandshake(SslTransportLayerTest.java:883)
        at 
app//org.apache.kafka.common.network.SslTransportLayerTest.testUngracefulRemoteCloseDuringHandshakeWrite(SslTransportLayerTest.java:833)
   ```
   
   We expected the channel state to be `AUTHENTICATE` or `READY`, but got 
`EXPIRED`. Checking the test, we're not expecting expired state at all, but set 
a 5 secs idle timeout in selector, which is not enough when machine is busy. 
Increasing the `connectionMaxIdleMs` to 10 secs to make the test reliable.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to