What could be the reason? SSLProtocolException: Handshake message sequence violation, 1?

Question

Java

From time to time, but not always , in the server part of the application, when the client connects, such an error takes off. Departure conditions have not yet been set - sometimes occurs when the server is started under the debugger, but not 100% of this.

javax.net.ssl.SSLProtocolException: Handshake message sequence violation, 1
  at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1546)
  at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:528)
  at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:802)
  at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:766)
  at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
        ....
Caused by: javax.net.ssl.SSLProtocolException: Handshake message sequence violation, 1
  at sun.security.ssl.HandshakeStateManager.check(HandshakeStateManager.java:362)
  at sun.security.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:212)
  at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
  at sun.security.ssl.Handshaker$1.run(Handshaker.java:970)
  at sun.security.ssl.Handshaker$1.run(Handshaker.java:967)
  at java.security.AccessController.doPrivileged(Native Method)
  at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1475)
        ....

(The stack trace of our code is cut out)

Google does not give anything sensible, mostly links to some bugs in Kafka, but we have our own application based on some open-source product. There is no experience with SSL.

Answer 1

This is a bug in the JDK. Here is some information: https://github.com/jetty-project/jetty-alpn/issues/18