Skip to content

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

@devisbalsemin

Description

@devisbalsemin

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: improvementA minor improvement to an existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions