io.vertx.core.eventbus.ReplyException: No handlers for address io.vantiq.consumer.monitored.acbe1e09-2ed5-464b-bd32-2c05b179031b

Google Groups | Sean Fitts | 3 months ago
  1. 0

    Possible issue in management of handlers for the clustered event bus

    Google Groups | 3 months ago | Sean Fitts
    io.vertx.core.eventbus.ReplyException: No handlers for address io.vantiq.consumer.monitored.acbe1e09-2ed5-464b-bd32-2c05b179031b
  2. 0

    No handler for address Exception after a client node reconnects

    Google Groups | 6 months ago | Mikhail Severov
    io.vertx.core.eventbus.ReplyException: No handlers for address function-execution
  3. 0

    Server becomes unresponsive after error in handlebars markup occured

    GitHub | 2 months ago | tenitram
    io.vertx.core.eventbus.ReplyException: No handlers for address knotx.core.engine
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    java.lang.ClassCastException: java.lang.Long cannot be cast to [Lio.vertx.redis.impl.Reply;

    GitHub | 5 months ago | pmlopes
    io.vertx.core.eventbus.ReplyException: Timed out after waiting 5000(ms) for a reply. address: 136
  6. 0

    java.lang.ClassCastException: java.lang.Long cannot be cast to [Lio.vertx.redis.impl.Reply;

    GitHub | 5 months ago | hansen2014
    io.vertx.core.eventbus.ReplyException: Timed out after waiting 5000(ms) for a reply. address: 136

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. io.vertx.core.eventbus.ReplyException

      No handlers for address io.vantiq.consumer.monitored.acbe1e09-2ed5-464b-bd32-2c05b179031b

      at io.vertx.core.eventbus.impl.HandlerRegistration.sendAsyncResultFailure()
    2. Vert.x Core
      EventBusImpl.deliverMessageLocally
      1. io.vertx.core.eventbus.impl.HandlerRegistration.sendAsyncResultFailure(HandlerRegistration.java:118)
      2. io.vertx.core.eventbus.impl.EventBusImpl.deliverMessageLocally(EventBusImpl.java:349)
      2 frames
    3. io.vertx.core
      ClusteredEventBus.lambda$sendOrPub$4
      1. io.vertx.core.eventbus.impl.clustered.ClusteredEventBus.lambda$sendOrPub$4(ClusteredEventBus.java:221)
      1 frame
    4. io.vertx.spi
      HazelcastAsyncMultiMap.lambda$get$3
      1. io.vertx.spi.cluster.hazelcast.impl.HazelcastAsyncMultiMap.lambda$get$3(HazelcastAsyncMultiMap.java:116)
      1 frame
    5. Vert.x Core
      ContextImpl.lambda$wrapTask$2
      1. io.vertx.core.impl.FutureImpl.checkCallHandler(FutureImpl.java:158)
      2. io.vertx.core.impl.FutureImpl.setHandler(FutureImpl.java:100)
      3. io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:271)
      4. io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:316)
      4 frames
    6. Netty
      SingleThreadEventExecutor$5.run
      1. io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
      2. io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418)
      3. io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)
      4. io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)
      4 frames
    7. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)
      1 frame