Multiple Application Contexts created when running launch project with aws-lambda

[trynow-david]

Expected Behavior

When you create a new launch project from the micronaut.io/launch, include the aws-lambda project, and run the application via ./gradlew run command, the application context is ran twice. This is due to the AwsApiProxyTestServer embedded server class building and running a new application context. The Jetty embedded server class you get if you change the micronaut runtime to jetty rather than lambda_java does not create a new application context but uses the one that already exists so I believe this is a bug.

Actual Behaviour

Multiple application contexts are built and run.

Steps To Reproduce

Download the basic launch project with aws-lambda feature. Below is the config I used.

applicationType: default
defaultPackage: com.example
testFramework: junit
sourceLanguage: kotlin
buildTool: gradle_kotlin
features: [app-name, aws-lambda, aws-lambda-events-serde, aws-lambda-handler-default, gradle, http-client-test, junit, kotlin, kotlin-application, ksp, logback, micronaut-aot, micronaut-build, micronaut-http-validation, properties, readme, serialization-jackson, shade, snapstart, static-resources, x86]

To show the effect, I created a simple Singleton that runs on a schedule which then you can see is created twice.

@Singleton
class HomeService {
    companion object {
        private val LOG: Logger = LoggerFactory.getLogger(this::class.java)
    }
    init {
        LOG.info("HomeService initialized with UUID: ${UUID.randomUUID()}")
    }

    @Scheduled(fixedDelay = "5s")
    fun test(){
        LOG.info("HomeService test method called")
    }
}

Environment Information

• Mac OS 14.5 (23F79)

Example Application

No response

Version

micronautVersion=4.7.6

[mplanchant]

I think this problem is manifesting itself when trying to use the new embedded HTTP server.

$ ./gradlew run

> Task :run
08:48:47.224 [main] INFO  i.m.c.DefaultApplicationContext$RuntimeConfiguredEnvironment - Established active environments: [local]
08:48:47.402 [main] INFO  i.m.c.DefaultApplicationContext$RuntimeConfiguredEnvironment - Established active environments: [local]
08:48:47.462 [main] ERROR io.micronaut.runtime.Micronaut - Error starting Micronaut server: Error starting HTTP server: Error instantiating bean of type  [io.micronaut.servlet.http.server.HttpServerEmbeddedServer]

Message: Address already in use
Path Taken:
new @j.i.Singleton i.m.s.h.s.DiscoveryServerStartedEventPublisher(ApplicationConfiguration applicationConfiguration, EmbeddedServer embeddedServer, ApplicationEventPublisher<ServiceReadyEvent> applicationEventPublisher)
\---> new @j.i.Singleton i.m.s.h.s.DiscoveryServerStartedEventPublisher(ApplicationConfiguration applicationConfiguration, [EmbeddedServer embeddedServer], ApplicationEventPublisher<ServiceReadyEvent> applicationEventPublisher)
      \---> new @j.i.Singleton i.m.s.h.s.HttpServerEmbeddedServer(ApplicationContext applicationContext, @Named("HttpServer") ApplicationContextProvider applicationContextProvider, ApplicationConfiguration applicationConfiguration, HttpServerConfiguration httpServerConfiguration, ApplicationEventPublisher<ServerShutdownEvent> serverShutdownEventPublisher, [HttpServer server])
io.micronaut.http.server.exceptions.HttpServerException: Error starting HTTP server: Error instantiating bean of type  [io.micronaut.servlet.http.server.HttpServerEmbeddedServer]

[graemerocher]

perhaps this can be fixed somehow in the test server by modifying it to only load a subset of the bean definitions needed to run the server

[mplanchant]

Is there a work around for this? It's a bit of pain no being able to run the app locally with ./gradlew run.

[graemerocher]

well I guess you could use some other runtime for local dev (like servlet-jetty) in the meantime

[mplanchant]

well I guess you could use some other runtime for local dev (like servlet-jetty) in the meantime

How would I do this? If I try ./gradlew clean run -Pmicronaut.runtime=jetty, I get:

14:15:26.463 [main] ERROR io.micronaut.runtime.Micronaut - Error starting Micronaut server: Multiple possible bean candidates found: [JettyServer, HttpServerEmbeddedServer]
io.micronaut.context.exceptions.NonUniqueBeanException: Multiple possible bean candidates found: [JettyServer, HttpServerEmbeddedServer]

[trynow-david]

Changing the local runtime to netty works for me. Note I also had to add some libs that the lambda_java runtime includes by default so you might as well. For me it's these 3.

        implementation(mn.micronaut.aws.lambda.events.serde)
        implementation(mn.micronaut.function.aws)
        implementation(mn.micronaut.function.aws.api.proxy)

I'm not sure why you'd have multiple bean candidates. You could try to debug where that error is coming from and see where the HttpServerEmbeddedServer is coming from then see if you actually need that lib as part of your runtime.

[mplanchant]

Using ./gradlew clean run -Pmicronaut.runtime=jetty is working for me now. I had to remove the following dep:

developmentOnly(mn.micronaut.function.aws.api.proxy.test)