quarkus: OOM with QuarkusTestResourceConfigurableLifecycleManager

Describe the bug

I replaced our wiremock integration tests with a QuarkusTestResourceLifecycleManager approach. Instead of starting und stopping the wiremock server in the junit BeforeAll and AfterAll methods, I provide a class the looks like the following:

class WiremockServerTestResource: QuarkusTestResourceConfigurableLifecycleManager<WithWiremockedRemoteApis> {
    val server = WireMockServer(WireMockConfiguration.options().dynamicPort())
    val name = AtomicReference<String>()

    override fun init(annotation: WithWiremockedRemoteApis) {
        name.set(annotation.name)
    }

    override fun start(): MutableMap<String, String> {
        val mappingSource = JsonFileMappingsSource(ClasspathFileSource("wiremock"))
        mappingSource.loadMappingsInto(InMemoryStubMappings())

        server.loadMappingsUsing(mappingSource)
        server.start()

        return mutableMapOf(
            "org.acme.UserClient/mp-rest/url" to server.baseUrl()
        )
    }

    @Synchronized
    override fun stop() {
        server.stop()
    }
}


@QuarkusTestResource(WiremockServerTestResourceSlow::class)
@Retention(AnnotationRetention.RUNTIME)
@Target(AnnotationTarget.CLASS)
annotation class WithWiremockedRemoteApis(
    val name: String = "Frufru"
)

I annotated all integration tests with @WithWiremockedRemoteApis and basically this approach looks pretty charming. My problem is though, that my tests ran into an OOM with this approach. On my local macbook this does not happen all the time but on our gitlab runners (with lower resources), the tests do not work at all and fail with an OOM.

I also created a sample project that at least shows, that this approach is much slower than the static initialisation: https://github.com/u6f6o/slow_tests I could not reproduce the OOM though 😦 I think there might be an issue with the QuarkusTestResourceConfigurableLifecycleManager as the tests, even for this simple project are much slower in the test setup phase:

Expected behavior

Tests should be almost as fast as with static wiremock initialisation and should not run in to an OOM.

Actual behavior

No response

How to Reproduce?

1.) Check out https://github.com/u6f6o/slow_tests 2.) Run tests in org.acme.static 3.) Run tests in org.acme.quarkuslifecycle 4.) Compare results (OOM does not occur in this example though)

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response