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
, 9 months ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
via Stack Overflow by Anna
, 3 months ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
via GitHub by allandel73
, 2 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, 11 months ago
Inbound closed before receiving peer's close_notify: possible truncation attack?
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 org.apache.kafka.common.network.Selector.poll(Selector.java:281)	at kafka.network.Processor.run(SocketServer.scala:413)	at java.lang.Thread.run(Thread.java:722)