Hi;
we are getting several "Duplication sessionId created" warnings, generated from SecurityMgr.java:login:148, using konakart v3.2.0.0.
The full warning text is: " Duplicate sessionId created. We advise to clear out old sessions using the admin app since thi will affect performance."
Is the affect on performance the extra time required to recalculate and persist a sessionId, in the event of a duplicate? Or something more sinister?
I've checked our session table and we have 45,000 (!!!) sessions. What causes these sessions to accumulate and what can we do to reduce this build-up from occurring? I know there's an admin function to remove old sessions, but I'm trying to understand the root cause, eg: is this a side effect of a Denial of Service attack?
-- Clinton
we are getting several "Duplication sessionId created" warnings, generated from SecurityMgr.java:login:148, using konakart v3.2.0.0.
The full warning text is: " Duplicate sessionId created. We advise to clear out old sessions using the admin app since thi will affect performance."
Is the affect on performance the extra time required to recalculate and persist a sessionId, in the event of a duplicate? Or something more sinister?
I've checked our session table and we have 45,000 (!!!) sessions. What causes these sessions to accumulate and what can we do to reduce this build-up from occurring? I know there's an admin function to remove old sessions, but I'm trying to understand the root cause, eg: is this a side effect of a Denial of Service attack?
-- Clinton