Dirk,
> I have run NullLocker now for a while and it looks like the problem
> with the session data still persists. It happens not as much as with
> SysVSemaphoreLocker but is still observable. Maybe I have found one
> more point of interest here:
>
> Gerald suggested to check that the session object is really destroyed
> which means that it should be saved. I checked this directly in
> Apache::Session with a warning: I could observe no occasion where it
> wouldn't be destroyed. Also when the case happened that session data
> seems not to be changed I checked the session data field of the
> session table in the data base. The interesting thing seems to be that
> the data has changed in the database but somehow would not be
> retrieved from the next page which still gets that old values.
>
Have you tried to explicitly turn off caching like Ceasr suggested. (I
append the mail again at the end)
> Next thing is to switch from Apache::Session 1.02 to 1.03
>
There is no change from 1.02 to 1.03 (only unused code has changed), so this
will not change anything.
Gerald
-----Original Message-----
From: Cesar Bonadio [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 18, 2000 5:51 PM
To: [EMAIL PROTECTED]
Subject: udat persistence issues possible solution
Dear Gerald
I saw all the persistence messages in the list and we are in a project
and we had
the same problems we tried several optoins but the only one that help
was
set NullLocker in the DBIStore, but even with that the problem occured
less frequently
we found that if you set the page to do not cache that solved our
problems
[-
$http_headers_out{'pragma'} = "no-cache";
$http_headers_out{'expires'} = "0";
we have been with this configuration and NullLocker for 2 days and no
problems so far.
this is tests system but soon will go to production.
Hope that helps
Best Regards
Cesar Bonadio
--
----------------------------------------------------------
Cesar A. Bonadio Picture Internet
<[EMAIL PROTECTED]> Rua Sud Mennucci 331
Tel/Fax:011 5084-0028 Sao Paulo -SP-Brasil-04017-080
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
