vertx-eventbus

问题 From my routing verticle which has route URL, I want to send RoutingContext object to another verticle. I believe we can only use vertx.eventBus().send() to send message from routing verticle to some other action verticle. Can I send RoutingContext object as a message? In router verticle I am doing vertx.eventBus().<RoutingContext>send("address", routingContext) and in consumer verticle I am doing vertx.eventBus().<RoutingContext>consumer("address").handler(message -> { RoutingContext

问题 From my routing verticle which has route URL, I want to send RoutingContext object to another verticle. I believe we can only use vertx.eventBus().send() to send message from routing verticle to some other action verticle. Can I send RoutingContext object as a message? In router verticle I am doing vertx.eventBus().<RoutingContext>send("address", routingContext) and in consumer verticle I am doing vertx.eventBus().<RoutingContext>consumer("address").handler(message -> { RoutingContext

问题 Here I am mocking it and expecting nothing from the method, but when I send the request body through eventbus request was going inside the method, which I am not expecting. Can anyone help me with this issue? I didn't mocked any JDBC client and in the config file too I am giving empty credentials, since I am mocking it. public class verticle extends AbstractVertcile { private void jdbcCall(JsonArray data, Future<JsonArray> promise) { String first_name = data.getValue(first_name); String last

问题 I'm missing one piece of understanding of how Event Bus / Hazelcast works. Imagine a case with a consumer and a producer verticles communicating over the clustered EB. The consuming part is doing CPU / memory / IO-intensive calculations. When at some point due to the load the consumer is not able to handle the messages immediately, what is going to happen? Would the messages be queueed inside the ring-buffer and eventually be processed later (considering Netty's SingleThreadEventLoop limits

问题 I'm missing one piece of understanding of how Event Bus / Hazelcast works. Imagine a case with a consumer and a producer verticles communicating over the clustered EB. The consuming part is doing CPU / memory / IO-intensive calculations. When at some point due to the load the consumer is not able to handle the messages immediately, what is going to happen? Would the messages be queueed inside the ring-buffer and eventually be processed later (considering Netty's SingleThreadEventLoop limits