javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via kafka-users by Adam Kunicki, 1 year ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
via GitHub by TheMidgardWatcher
, 5 months ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
via GitHub by djtecha
, 1 year ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
via Google Groups by Nick Zhu, 7 months ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
via blackberry.com by Unknown author, 2 years ago
via blackberry.com by Unknown author, 2 years ago
javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1639)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1607)
at sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:1537)
at org.apache.kafka.common.network.SslTransportLayer.handshakeFailure(SslTransportLayer.java:723)
at org.apache.kafka.common.network.SslTransportLayer.handshake(SslTransportLayer.java:313)
at org.apache.kafka.common.network.KafkaChannel.prepare(KafkaChannel.java:68)
at kafka.network.Processor.run(SocketServer.scala:413)
at java.lang.Thread.run(Thread.java:722)

Users with the same issue

3 times, 4 months ago
5 times, 4 months ago
Once, 4 months ago
Once, 1 year ago
Once, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.