Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

path to be lazy initialized by injecting a provider to avoid this issue #543

Open
devisbalsemin opened this issue Mar 9, 2023 · 0 comments

Comments

@devisbalsemin
Copy link

Hello,
I'm using

<dependency>
          <groupId>io.micronaut.kubernetes</groupId>
          <artifactId>micronaut-kubernetes-operator</artifactId>
          <version>3.4.0</version>
</dependency>

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant