vellrya

  I manage sse connections as below (simplified): ``` val paidSSE = ConcurrentHashMap() //... sse("/path") { sse.onClose { for (tmpSse in paidSSE) { if (tmpSse.value==sse) { paidSSE.remove(tmpSse.key) break }...

Here are some additions after updating the server to Jooby 2.16.1. I created and use the following function to send SSE messages: ``` inline fun ServerSentEmitter.trySend(data: ServerSentMessage) { if (!this.isOpen)...

Hello, I am still using version 2.13.0 as it has no memory leaks. Should I try version 3.x, or has there been no change related to my problem?

Thanks, as soon as 3.0.0.M3 with Kotlin 1.8.0 appears, I will try the new version)

 This is the dependency tree with Kotlin 1.6.21, I'll report on the result.

I tried it first with the configuration you suggested and found no memory leaks. Then removed all the exclusions and switched completely to version 2.16.1 and in 64 hours of...

Unfortuanetely, the issue has not been fixed. This is my mistake - I changed the dependencies in the .pom file, but forgot to change the output artifacts. In fact, there...

So, here are the results using the dependency versions you specified in https://github.com/jooby-project/jooby/issues/2607#issuecomment-1377134016: > [2023-01-25 19:06:23,821]-[main] INFO io.undertow - starting server: Undertow - 2.2.14.Final > [2023-01-25 19:06:23,828]-[main] INFO org.xnio -...

Test on Jooby 2.13.0, no memory leaks. No changes made to code - just different versions of dependencies. 

I was curious to find out in which version the memory leak appeared in order to localise the problem. **Jooby 2.14.0 .. 2.14.2 - no leak:** > [2023-01-26 11:55:34,780]-[main] INFO...