EventBus ConsumeEvent starts consuming messages even before the engine is up

[vishnupriya19]

I have something like below.
@RunOnVirtualThread @ConsumeEvent(value = "xxx, codec = ServiceExceptionMessageCodec.class, local = false) public void consumeMessages(Message<JsonObject> msg) { logger.debug("request has come to eventbus", msg.address()); // processing logic }
In production environment, the event bus starts consuming messages even before my engine is up and ready and is throwing exceptions, can you help me in solving this?
If I manually register the consumers after the engine start, then we loose out on the VirtualThread Annotation.

[mkouba]

before my engine is up and ready

What engine do you have in mind? The @ConsumeEvent method is executed when a message is received. You might be able to block the execution from within the consuming method until the engine is ready but then you risk pinned carrier threads. An alternative solution is to store the received events in a queue-like structure and process them separately, e.g. in a scheduled method.

If I manually register the consumers after the engine start, then we loose out on the VirtualThread Annotation.

You can also inject the VirtualThread ExecutorService and use it in the manually registered consumers.