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 Stack Overflow by cbm64
, 1 year ago
Request timed out to localhost/127.0.0.1:8080 of 60000 ms
via Google Groups by Rodion Ovodnev, 1 year ago
Request timed out to /127.0.0.1:12900 of 10000 ms
via Stack Overflow by jakob
, 1 year ago
Request timed out to cool.api.com/212.16.165.50:443 of 120000 ms
via GitHub by farhatakrout
, 2 years ago
Request timed out to ecul0613 / 10.30.193.95: 10210 of 60000 ms
via GitHub by thebox-dev
, 2 years ago
Read timeout to /172.31.7.18:12900 of 60000 ms
java.util.concurrent.TimeoutException: Request timed out to localhost/127.0.0.1:8080 of 60000 ms	at com.ning.http.client.providers.netty.request.timeout.TimeoutTimerTask.expire(TimeoutTimerTask.java:47)	at com.ning.http.client.providers.netty.request.timeout.RequestTimeoutTimerTask.run(RequestTimeoutTimerTask.java:48)	at org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:556)	at org.jboss.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:632)	at org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:369)	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)	at java.lang.Thread.run(Thread.java:745)