(This question stems from an issue first brought up
here<https://groups.google.com/forum/?fromgroups=#!topic/web2py/iAlrv6yaHWk>
)
We store user sessions in the DB using the web2py_session_{app} table.
Inspecting the table, we've noticed a strange pattern happening over and
over again:
Many of our app actions update the session. Generally, when a user hits the
app and causes a session update, a single session record associated with
that client gets updated in the DB. Additionally, however, we're noticing a
large number of one-time 'orphan' session records which will also be tied
to the same IP, but that have created_datetime = modified_datetime, meaning
they were never updated.
These one-time session records are usually spaced a few seconds or minutes
apart, as if they were being created once per request. Some days there are
dozens of these records, other days there are none. Each of these session
records has its own unique key.
It's happening in both remote production (LAMP) and local dev (MAMP)
environments. In both environments, however, no session records exist that
are older than 3/10 (Today is 4/17), so something is clearing them out.
I can't make sense of this. Ideas?
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
