Github user JohnKiel commented on the issue:
https://github.com/apache/tomcat/pull/41
If you use SELECT FOR UPDATE, then you'll also need to start and commit a
transaction, with the overhead that entails. If the record is modified or even
deleted between the time the SELECT
GitHub user JohnKiel opened a pull request:
https://github.com/apache/tomcat/pull/41
Check and update session record if one already exists.
Check and update session record if one already exists, instead of deleting
and re-inserting new record.
You can merge this pull request into