Duplicate sessions with sessioncluster

We use Lucee 5.0 and include “this.sessioncluster=true” to use MySQL for
session storage. We have added a primary key on the “cfid, name” fields.

I noticed we get a number of entries in our scope.log file (on average a
few per day… not enough to have caused any dramas) with a message like
“Duplicate entry ‘0d01a023-f13e-456b-996f-5fcca88c8e29-tennis’ for key
‘PRIMARY’”.

Is this primary key a bad idea? Should Lucee not be checking for an
existing record anyway, so that these duplicates do not occur? Is this a
bug I should report or should I just get rid of the index?

Thanks,
Simon

Since a session needs to be identified uniquely, a unique index is a very
good idea in terms of performance imho. What about the session age? When
are inactive sessions removed from the database? Maybe lucee just reuses
them, but they are just not removed from the database.Am Dienstag, 24. Januar 2017 23:03:16 UTC+1 schrieb Simon Goldschmidt:

We use Lucee 5.0 and include “this.sessioncluster=true” to use MySQL for
session storage. We have added a primary key on the “cfid, name” fields.

I noticed we get a number of entries in our scope.log file (on average a
few per day… not enough to have caused any dramas) with a message like
“Duplicate entry ‘0d01a023-f13e-456b-996f-5fcca88c8e29-tennis’ for key
‘PRIMARY’”.

Is this primary key a bad idea? Should Lucee not be checking for an
existing record anyway, so that these duplicates do not occur? Is this a
bug I should report or should I just get rid of the index?

Thanks,
Simon