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 GitHub by hansen2014
, 1 year ago
via GitHub by pmlopes
, 1 year ago
via Google Groups by Hoobajoob, 1 month ago
Timed out after waiting 30000(ms) for a reply. address: fc60e114-4a40-48c0-befe-013c0bfe0b7b
via Google Groups by Gadi Eichhorn, 10 months ago
Timed out after waiting 2000(ms) for a reply. address: 10
via GitHub by tenitram
, 1 year ago
via Google Groups by Mikhail Severov, 2 years ago
No handlers for address function-execution
io.vertx.core.eventbus.ReplyException: Timed out after waiting 5000(ms) for a reply. address: 136 at io.vertx.core.eventbus.impl.HandlerRegistration.sendAsyncResultFailure([vertx-core-3.3.0.jar:na] at io.vertx.core.eventbus.impl.HandlerRegistration.lambda$new$0([vertx-core-3.3.0.jar:na] at io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle([vertx-core-3.3.0.jar:na] at io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle([vertx-core-3.3.0.jar:na] at io.vertx.core.impl.ContextImpl.lambda$wrapTask$3([vertx-core-3.3.0.jar:na] at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks([netty-common-4.1.1.Final.jar:4.1.1.Final] at[netty-transport-4.1.1.Final.jar:4.1.1.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$[netty-common-4.1.1.Final.jar:4.1.1.Final] at Source)[na:1.8.0_91]