Hi, I would just like to tune in here. I am using Apache::Session 1.53
also with postgres and have the problem that sessions are not closed
in any case. I am also using Embperl 1.3.0 but maintaining the session
variable on my own. The effect is that when apache is restarted
everything works fine but after some time (or heavy load) some
sessions start not to store modification anymore. This culminates
after a while into an usable system which needs a restart. The
application code needs very careful examination for closing the
session in all cases.
To find out if it is the application that is not closing the session
or if there is a problem in Apache::Session or in the database is very
hard to track down. I checked all the application code and using
vanilla Apache::Session::Store::Postgres with FOR UPDATE, ie. using
locks on the session table. I would appreciate any suggestion on how
to debug/find unclosed sessions on a high volume site. Eg. one could
work with timeouts, this is when a session is not closed after some
period of time a warning would be issued. This would help much to find
out who is not closing the session.
Regards,
Dirk
