GitHub user aschwarte10 edited a comment on the discussion: [Bug] Unexpected session expiration behavior on ARM64 architecture (Concurrency Issue)
Hi @lprimak , do you mean a `org.apache.shiro.session.SessionListener`? If I remember correctly we have done this, however, the exception (at least in one control flow path) was thrown prior to reaching the session listener (i.e. the session listener was not called). I can try once more during today, if I can get a stacktrace from the session listener. > FYI this is a pretty unusual situation. Usually, high-concurrency happens on > different sessions and not the same one. Our JMeter workload to hammer the server with concurrent requests on the same session is somewhat _extreme_, however, this was the only way we found that increases the likelyhood of the issue. In our real application we also do have multiple sessions and from my expectation a realistic workload from individual ones for a client-server application. GitHub link: https://github.com/apache/shiro/discussions/2447#discussioncomment-15472446 ---- 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]
