Hello, Did anyone had problems with Jetty Session Management with Karaf 4.2.x ?
After updating my Karaf and Java I've executed load tests that simulated many concurrent users. The test went through, and I've waited until all remaining sessions get scavenged (I have Prometheus metrics registered in session listener), and after that I've repeated the test with smaller number of users and to my surprise, the container died immediately. I have health checks that do sample memory-intensive operation, that should, in theory, kill container when Java reaches OutOfMemory, but none of them has triggered. I've tried to heal the container restarting DB connection pool, etc., then I've got an idea that the Jetty could be broken, and after restarting pax-web-jetty bundle, the container went alive. So it looks like, something went stuck inside the Jetty container. I'll try adding creating HttpSession to health checks and make a test that logs in/out a few users for a longer period of time to try to spot the problem more exacly... Has someone notices similar unstable behavior with Jetty? Some resources get not released internally? Some undocumented session limit was reached? Thanks for any input, Lukasz Lech
