max-active-session enables the use of a near-cache within the HotRod client used by hotrod-session-management.
Currently, session expiration is handled by applying a max-idle to a session's creation metadata. However, if near caching is enabled, subsequent reads of this entry do not touch the infinispan server, which means that session will always expire according to the session-timeout from the time they were created - regardless of how often the are accessed.