Hello,
I have now been running the system with the NullLocker for the last couple
of days and it has greatly improved the %udat persistence problem. However,
the problem still occurs.
The characteristics of the problem has however somewhat changed after I
started using the NullLocker. The problem does not occur nearly as often as
before but when it occurs I often have to restart the apache server to get
any data from %udat while when using the SysVSemaphoreLocker I often just
had to wait some time and then refresh the page.
Anyhow, the improvement was considerable when moving to the NullLocker but,
as Gerald said, %mdat will most likely be affected,at least in my case, as
there it is very likely that the same page will be fetched simultaneously.
Any suggestion on where to go from here?
Dirk, I look forward to hear how the NullLocker affected your system.
Ragnar
-----Original Message-----
From: Dirk Lutzebaeck [mailto:[EMAIL PROTECTED]]
Sent: 12 May 2000 08:46
To: Gerald Richter
Cc: Ragnar Hakonarson; [EMAIL PROTECTED]
Subject: RE: problems with %udat persistance
Gerald Richter writes:
> >
> >
> > Hi, I would just like to tune in here. I observe same occasional
> > problems that you describe. I'm using also the samy config, Postgres
> > 6.5.3, Apache::Session 1.02 with Cookies, SysVSemaphoreLocker and
> > Embperl 1.2.1 on Linux 2.2.10. What helps me is to restart the apache
> > process.
> >
>
> This could by a locker problem, because locks will be released when you
> restart apache. Could you try the NullLocker? If the problem persist we
have
> to search in another direction, if the problem went away by using the
> NullLocker, then it's more likey an Embperl problem (that Embperl doesn't
> relaese the session under some circumstances)
Ok, I have set it to NullLocker now and report what happens. What do I
loose if I'm using NullLocker instead of SysVSemaphoreLocker? Btw. I'm
not using %udat but Apache::Session (1.02) directly.
Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
