.SslHandshakeTimeoutException: handshake timed out after 10000ms in error logs | Community
Skip to main content
A
AK86
New Participant
September 13, 2022
Solved

.SslHandshakeTimeoutException: handshake timed out after 10000ms in error logs

  • September 13, 2022
  • 1 reply
  • 7016 views

Hi All,

 

I am getting ssl handshake timeout error in error logs:

13.09.2022 13:42:37.432 *WARN* [reactor-tcp-nio-1] reactor.netty.http.client.HttpClientConnect [id:c951411d, L:/151.110.165.138:44510 - R:***-aem.staging.percolate.services/18.214.64.54:443] The connection observed an error
io.netty.handler.ssl.SslHandshakeTimeoutException: handshake timed out after 10000ms
at io.netty.handler.ssl.SslHandler$5.run(SslHandler.java:2060) [com.percolate.aem-plugin.core:2.0.0]
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)
13.09.2022 13:42:37.438 *WARN* [reactor-tcp-nio-2] reactor.netty.http.client.HttpClientConnect [id:f3d14a6c, L:/151.110.165.138:43334 - R:***-aem.staging.percolate.services/52.6.166.84:443] The connection observed an error
io.netty.handler.ssl.SslHandshakeTimeoutException: handshake timed out after 10000ms
at io.netty.handler.ssl.SslHandler$5.run(SslHandler.java:2060) [com.percolate.aem-plugin.core:2.0.0]
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)

This causing performance issue and have to restart server when it is unresponsive. Kindly provide your inputs to fix this issue.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

Hello @ak86 

 

It seems to be certificate issue.

 

Ensure that the root certificates used to validate (target) server certificates are up to date. CAs occasionally update their root certificates, and older versions may not recognize newer certificates.

 

1 reply

aanchal-sikka
aanchal-sikkaAccepted solution
New Participant
September 7, 2023

Hello @ak86 

 

It seems to be certificate issue.

 

Ensure that the root certificates used to validate (target) server certificates are up to date. CAs occasionally update their root certificates, and older versions may not recognize newer certificates.

 

Aanchal Sikka
    Terms & ConditionsAccessibility statement

    Loading footer...