Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8279649

sun/security/ssl/SSLSessionImpl/NoInvalidateSocketException.java failing intermittently in loom repo

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: repo-loom
    • Fix Version/s: None
    • Component/s: security-libs
    • Labels:

      Description

      sun/security/ssl/SSLSessionImpl/NoInvalidateSocketException.java is failing intermittently in the loom repo, at least when running with the jtreg wrapper. At this time, the loom repo is sync'ed with jdk-19+4. Typical output is:

      ----------messages:(4/201)----------
      command: main NoInvalidateSocketException TLSv1.3
      reason: User specified action: run main/othervm NoInvalidateSocketException TLSv1.3
      Mode: othervm [/othervm specified]
      elapsed time (seconds): 19.957
      ----------configuration:(0/0)----------
      ----------System.out:(265/20029)----------
      3184910571885024: Server Listener Thread: Listening on 0.0.0.0/0.0.0.0:42041
      3184910680217398: Server Listener Thread: Accepted connection from /100.104.98.156:55696
      3184910683965069: Main Client Thread: Opened SSLSocket@3ea44a5b
      3184910687276980: Main Client Thread: Started handshake on SSLSocket@3ea44a5b
      3184910893757714: Main Client Thread: Finished handshake on SSLSocket@3ea44a5b
      3184910894145153: Main Client Thread: *** OPENED NEW SESSION ***: Session(1641654071137|TLS_AES_256_GCM_SHA384)
      3184910894546672: Client Reader Thread: Started reading from SSLSocket@3ea44a5b
      3184910904970406: Main Client Thread: Closing SSLSocket@3ea44a5b
      3184910910149233: Main Client Thread: Closed SSLSocket@3ea44a5b
      3184910910198833: Server Reader Thread: Received: -1 bytes of data

      3184910917871494: Client Reader Thread: Exception reading from SSLSocket@3ea44a5b: java.net.SocketException: Socket closed
      java.net.SocketException: Socket closed
      at java.base/sun.nio.ch.NioSocketImpl.endRead(NioSocketImpl.java:251)
      at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:330)
      at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:353)
      at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:804)
      at java.base/java.net.Socket$SocketInputStream.read(Socket.java:993)
      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:1455)
      at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:1059)
      at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:966)
      at NoInvalidateSocketException.readFromSSLSocket(NoInvalidateSocketException.java:249)
      at NoInvalidateSocketException$ReaderThread.run(NoInvalidateSocketException.java:180)
      3184911422159017: Main Client Thread: *** Session(1641654071137|TLS_AES_256_GCM_SHA384) IS VALID ***

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jnimeh Jamil Nimeh
              Reporter:
              alanb Alan Bateman
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: