I have noticed within the
Apache::Session::Store::Oracle module that it uses a
SELECT a_session FROM sessions WHERE id = ? FOR UPDATE
If a user clicks the stop button in their browser during a process (IE during a session update or setting the session) and then clicks another link
this will sometimes cause apache to hang and the user must restart their browser. This will also cause the previous update
(UPDATE sessions SET a_session = ? WHERE id = ?) Oracle session to hang within Oracle. Has anyone else on the list seen this problem?
It shouldn't cause a hang because Apache::DBI issues a rollback from a cleanup handler after every request. You can verify that this is happening by turning on the DEBUG flag for Apache::DBI. See the Apache::DBI docs.
Last question
Apache::DBI->setPingTimeOut($data_source, $timeout)
What is your question about it?
- Perrin
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
