Session timeout not working
Periodically, we reach our maximum of concurrent sessions, and everyone is locked out with this message: This system currently has the maximum number of concurrent users logged in.
However, the real problem seems to be that closed sessions are not being cleared. The number of rows in the ACTIVESESSION table equals our concurrent license count, even though few of these rows actually represent active users.
Note that this takes a while to develop; after restarting the service, Yellowfin will run okay for several weeks.
Is there some configuration change that I can make to help Yellowfin be more reliable? Our session-timeout setting in web.xml is set to 30 minutes (but seems to not be working.)
Also, I was thinking of creating a scheduled task that would delete all rows from ACTIVESESSION during the night. Would that help with this issue, or just create more problems?