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

Samebug tips

  1. ,
    Expert tip

    Downgrading to 4.0.23.FINAL seems to fix this issue. As of 04/26/2017 it wasn't fixed yet in newer versions.

Solutions on the web

via Stack Overflow by georgeatkins
, 1 year ago
javax.net.ssl.SSLHandshakeException: Handshake failed
via GitHub by jingene
, 1 year ago
javax.net.ssl.SSLHandshakeException: error:00000000:lib(0):func(0):reason(0)
via GitHub by ywelsch
, 2 weeks ago
javax.net.ssl.SSLException: Received close_notify during handshake
via GitHub by alexbarta
, 3 months ago
javax.net.ssl.SSLHandshakeException: General SSLEngine problem
via GitHub by ranjeet29
, 8 months ago
javax.net.ssl.SSLHandshakeException: General SSLEngine problem
via GitHub by kiranduba
, 8 months ago
javax.net.ssl.SSLHandshakeException: General SSLEngine problem
io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Handshake failed	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:442)	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:248)	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)