Vedran Pavic

I'm afraid we're blocked here until testcontainers/testcontainers-java#369 is addressed.

Hi @bsideup, your workaround did help us to get things working, this issue is only about memory leak warnings we're encountering.

We're still experiencing these with TestContainers `1.7.1`: ``` Apr 20, 2018 2:26:54 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads WARNING: The web application [ROOT] appears to have started a thread named [ducttape-0] but has...

testcontainers/testcontainers-java#651 is tracking this on TestContainers side.

Thanks for the update @kiview. @rwinch In light of Kevin's [comment on testcontainers/testcontainers-java#651](https://github.com/testcontainers/testcontainers-java/issues/651#issuecomment-429439781) do you agree that we could simply live with this?

> it can still leak memory if it isn't explicitly shutdown in an environment where the JVM process might out live the scope of the application. Yeah, I'm aware of...

> seems like MapSessionRepository isn't considered "production-worthy" and perhaps this is a known issue already This exactly is the case and I think this could be documented more clearly (both...

This is basically a duplicate of #529.

@joshiste Metrics are probably something worth looking at from a higher level. A while ago I opened #1495 to consider adding Micrometer integration. Please track (and vote) that issue if...

That indeed helps, thanks. Having taken a closer look at the project build now, shouldn't `api` configuration be used here (instead of `implementation`): https://github.com/asciidoctor/asciidoctor-gradle-plugin/blob/34f2cf13abec169ca7e4e3c0b666a3ba46848260/jvm-pdf/build.gradle#L14