Hello Armando,
The `EmbeddedEventStore` will give you that warning if the EventConsumer can not longer tag along with the global event stream.
This global event stream is used to minimize the number of open database connections needed to the domain event entry table.
In such a scenario, the EventConsumer thread will automatically switch to a local event stream.
It should thus not mean you'd have to do anything specific within Axon, as the consumer will proceed on it's own.
From your response I however get the assumption it just shuts down any further event processing.
Is this actually the case? Have you been able to confirm that whilst that warning popped up your TrackingEventProcessor were still receiving events?
The reason you're receiving this error is very likely because (assumption incoming!) your TrackingEventProcessor tries to update a view, requires a connection for that from Hikari, but since it doesn't get any it waits until it receives one.
The waiting for that connection takes so long however, that the EventConsumer for the given TrackingEventProcessor is fallen behind compared to the others.
As said, it will (or should, if this is not the case in your application) now consume events in a separate thread.
Hope we can figure this out!
Cheers,
Steven