You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the application runs I see this Warning message WARN i.m.context.DefaultBeanContext - The bean created event listener io.micronaut.scheduling.instrument.ExecutorServiceInstrumenter will not be executed because one or more other bean created event listeners inject java.util.concurrent.ExecutorService: [cep-operator] io.micronaut.kubernetes.client.operator.ResourceReconcilerCreatedListener --> io.micronaut.kubernetes.client.operator.ControllerFactory --> io.micronaut.kubernetes.client.operator.controller.LeaderElectingControllerBuilder --> io.kubernetes.client.extended.leaderelection.LeaderElectionConfig --> io.kubernetes.client.extended.leaderelection.Lock --> io.kubernetes.client.openapi.ApiClient --> java.util.concurrent.ExecutorService [cep-operator] Change at least one point in the path to be lazy initialized by injecting a provider to avoid this issue
I'm not a Micronaut expert but I'm looking into ControllerFactory.java I suggest to use Provider for @Named(TaskExecutors.IO) ExecutorService executorService) ... to remove the conflicts.
Thank you in advance for your feedback
The text was updated successfully, but these errors were encountered:
Hello,
I'm using
When the application runs I see this Warning message
WARN i.m.context.DefaultBeanContext - The bean created event listener io.micronaut.scheduling.instrument.ExecutorServiceInstrumenter will not be executed because one or more other bean created event listeners inject java.util.concurrent.ExecutorService: [cep-operator] io.micronaut.kubernetes.client.operator.ResourceReconcilerCreatedListener --> io.micronaut.kubernetes.client.operator.ControllerFactory --> io.micronaut.kubernetes.client.operator.controller.LeaderElectingControllerBuilder --> io.kubernetes.client.extended.leaderelection.LeaderElectionConfig --> io.kubernetes.client.extended.leaderelection.Lock --> io.kubernetes.client.openapi.ApiClient --> java.util.concurrent.ExecutorService [cep-operator] Change at least one point in the path to be lazy initialized by injecting a provider to avoid this issue
I'm not a Micronaut expert but I'm looking into ControllerFactory.java I suggest to use Provider for
@Named(TaskExecutors.IO) ExecutorService executorService)
... to remove the conflicts.Thank you in advance for your feedback
The text was updated successfully, but these errors were encountered: