GitHub user lprimak added a comment to the discussion: [Bug] Unexpected session expiration behavior on ARM64 architecture (Concurrency Issue)
Thanks for the stack trace - it might be very helpful. > Note that this happens on "random" times - in my JMeter workload I have seen > it after seconds This is weird. If your timeout is 1800 seconds (30 minutes) how can any session possibly expire after mere seconds? It would be helpful to register a session invalidation listener and print out stack traces there to help debug this. FYI this is a pretty unusual situation. Usually, high-concurrency happens on *different* sessions and not the same one. This might not be a very well tested situation, and it's entirely possible that the race condition is in Shiro code. It's also possible that the race condition is in the application code, or even an interaction or a combination of each. GitHub link: https://github.com/apache/shiro/discussions/2447#discussioncomment-15458052 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
