[11u] test NoInvalidateSocketException.java failing since 8274736

[Zhengyu Gu]

Hi Goetz,

I could not reproduce on Windows 10 neither, release and fastdebug. Are 
you still seeing failures?

Thanks,

-Zhengyu

On 1/11/22 09:47, Lindenmaier, Goetz wrote:
> Hi Zhengyu,
> 
> we see above test failing since it was pushed to 11.
> 
> It happens on all platforms and machines sporadically, roughly
> 
> every third run.  It fails only in 11.
> 
> It seems not to be related to the two issues mentioned
> 
> In 8274736: 8274524 and 8277970. See also the log below.
> 
> Best regards,
> 
>    Goetz
> 
> …
> 
> 335262374876357: Main Client Thread: *** OPENED NEW SESSION ***: 
> Session(1640081713614|TLS_AES_256_GCM_SHA384)
> 
> 335262376364735: Client Reader Thread: Started reading from 
> SSLSocket at 4e5adc37
> 
> 335262388254500: Main Client Thread: Closing SSLSocket at 4e5adc37
> 
> 335262393544543: Main Client Thread: Closed SSLSocket at 4e5adc37
> 
> 335262393794628: Server Reader Thread: Received: -1 bytes of data
> 
> 335262395736985: Client Reader Thread: Exception reading from 
> SSLSocket at 4e5adc37: java.net.SocketException: Socket closed
> 
> java.net.SocketException: Socket closed
> 
>           at java.base/java.net.SocketInputStream.socketRead0(Native Method)
> 
>           at 
> java.base/java.net.SocketInputStream.socketRead(SocketInputStream.java:115)
> 
>           at 
> java.base/java.net.SocketInputStream.read(SocketInputStream.java:168)
> 
>           at 
> java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> 
>           at 
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> 
>           at 
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> 
>           at 
> java.base/sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70)
> 
>           at 
> java.base/sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1449)
> 
>           at 
> java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:1060)
> 
>           at 
> java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:967)
> 
>           at 
> NoInvalidateSocketException.readFromSSLSocket(NoInvalidateSocketException.java:249)
> 
>           at 
> NoInvalidateSocketException$ReaderThread.run(NoInvalidateSocketException.java:180)
> 
> 335262888066936: Main Client Thread: *** 
> Session(1640081713614|TLS_AES_256_GCM_SHA384) IS VALID ***
> 
> 335263891069822: Main Client Thread: Opened SSLSocket at 15cf8e42
> 
> 335263891241055: Main Client Thread: Started handshake on SSLSocket at 15cf8e42
> 
> …
> 
> javax.net.ssl|ALL|1A|Server Reader Thread|2021-12-21 10:15:26.646 
> GMT|SSLSessionImpl.java:242|Session initialized:  
> Session(1640081713614|TLS_AES_256_GCM_SHA384)
> 
> javax.net.ssl|ALL|10|Client Reader Thread|2021-12-21 10:15:26.661 
> GMT|SSLSessionImpl.java:242|Session initialized:  
> Session(1640081713614|TLS_AES_256_GCM_SHA384)
> 
> java.lang.RuntimeException: One or more sessions were improperly 
> invalidated.
> 
>           at 
> NoInvalidateSocketException.main(NoInvalidateSocketException.java:88)
> 
>           at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
> 
>           at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 
>           at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 
>           at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 
>           at 
> com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
> 
>           at java.base/java.lang.Thread.run(Thread.java:829)
> 
> JavaTest Message: Test threw exception: java.lang.RuntimeException: One 
> or more sessions were improperly invalidated.
> 
> JavaTest Message: shutting down test
>