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 Google Groups by Unknown author, 1 year ago
Handshake did not complete within 10000ms to https://host
via Google Groups by Ludovic Mercier, 2 years ago
Connection timed out: no further information to http://gatling-tool.org/
via Google Groups by Joe Barnes, 1 year ago
connection timed out: servicestest.digikey.com/23.48.158.130:443 to https://servicestest.digik ey.com/dkservices/Service.svc/soap
via Google Groups by Ayush Rastogi, 2 years ago
Connection refused: no further information: /146.122.188.52:7070 to http://146.122.188.52:7070/events.json?accessKey=9yg5nhR2Lj2Exyn2zWKMvyYjdI5lKE9K6RW6cWFa1t7tyucTSMdnLQ7DGvJzesvg
via Google Groups by Juan Antonio Cánepa Marquez, 1 year ago
https://repo1.maven.org/maven2/org/scalatra/scalatra_2.11/maven-metadata.xml
javax.net.ssl.SSLException: Handshake did not complete within 
10000ms	at org.jboss.netty.handler.ssl.SslHandler$1.run(SslHandler.java:444)	at org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:546)	at org.jboss.netty.util.HashedWheelTimer$Worker.notifyExpiredTimeouts(HashedWheelTimer.java:446)	at org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:395)	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)	at java.lang.Thread.run(Thread.java:745)