java.io.IOException

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


Solutions on the web3746

Solution icon of stackoverflow
via Stack Overflow by mevans7
, 7 months ago
javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?

Solution icon of web
via jboss.org by Unknown author, 1 year ago
javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?

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

Solution icon of googlegroups
via Google Groups by vseetharaman, 2 months ago
Write Channel Closed, possible SSL handshaking or trust fai lure

Solution icon of googlegroups
via Google Groups by Mark, 2 months ago
Write Channel Closed, possible SSL handshaking or trust failure

Solution icon of googlegroups
via Google Groups by Chandra Sekhar Rao, 2 months ago
Write Channel Closed, possible SSL handshaking or trust failure

Solution icon of googlegroups
via Google Groups by Ramesh Hosahalli, 2 months ago
Write Channel Closed, possible SSL handshaking or trust failure

Solution icon of oraclecommunity
via Oracle Community by 3004, 1 year ago
Write Channel Closed, possible SSL handshaking or trust failure [java]

Solution icon of oraclecommunity
via Oracle Community by 3004, 1 year ago
Write Channel Closed, possible SSL handshaking or trust fai lure

Solution icon of oraclecommunity
via Oracle Community by 3004, 1 year ago
Write Channel Closed, possible SSL handshaking or trust failure

Stack trace

  • java.io.IOException: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? at io.undertow.protocols.ssl.SslConduit.notifyReadClosed(SslConduit.java:577) at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:668) at io.undertow.protocols.ssl.SslConduit.read(SslConduit.java:530) at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127)[xnio-api-3.3.4.Final.jar:3.3.4.Final] at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:152) at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:130) at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:56) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)[xnio-api-3.3.4.Final.jar:3.3.4.Final] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)[xnio-api-3.3.4.Final.jar:3.3.4.Final] at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1059) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)[xnio-nio-3.3.4.Final.jar:3.3.4.Final] at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)[xnio-nio-3.3.4.Final.jar:3.3.4.Final] Caused by: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)[jsse.jar:1.8.0_71] at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)[jsse.jar:1.8.0_71] at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634)[jsse.jar:1.8.0_71] at sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:1561)[jsse.jar:1.8.0_71] at io.undertow.protocols.ssl.SslConduit.notifyReadClosed(SslConduit.java:575) ... 11 more

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

961 times, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
99 more bugmates