Dear Gerald,
Thanks for your quick response.
Cookies are being received and sent by the browser correctly. I am using a
cookie based login facility that works without any problems. Furthermore,
when reading the embperl debug file I see that the embperl session cookie id
is received by embperl from the browser, always.
I have detected that when embperl receives the session id that changes do
not get updated in the session database. Could the problem have anything to
do with the $Apache::Session::SysVSemaphoreLocker::nsems variable or the
mechanism related with it?
When I fetch a page and %udat is not correctly updated, or even not
containing any older data, I have to wait for some time before successfully
re-fetching the page with %udat responding correctly as opposed to
re-fetching the page instantly on failure. However, this is not 'always' the
case. Could it be that the SysVSemaphoreLocker mechanism is blocking access
to the row containing the data for the session id in question?
I suspect that the problem does not lie with embperl nor the browser. I
think the problem might be related with the persistence mechanism that
embperl uses. I always successfully retrieve database resources through DBI
(PostgreSQL) within my pages so I have a high degree of confidence with DBI.
Another point worth mentioning is that the session database is mySQL while
all other database resources through out the system are located in
PostgreSQL. For instance, the cookie based login mechanism I am using stores
it's cookie data in PostgreSQL and it never fails. I find it hard to believe
that mySQL is causing the problem as it seems to be used by many as the
session database. That leaves us with the SysVSemaphoreLocker mechanism as
the prime suspect, or?
Am I completely on the wrong track?
I am puzzled.
regards,
ragnar
-----Original Message-----
From: Gerald Richter [mailto:[EMAIL PROTECTED]]
Sent: 10 May 2000 18:57
To: Ragnar Hakonarson; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: problems with %udat persistance
>
> I use embperl's sessions management with mySQL under Suse Linux. I am
> experiencing non deterministic behaviour from embperl's session management
> as %udat does not always store or retrieve data appropriately. I
> use IE5
As Vladimir told us, early version of IE 5 have problems with cookie. So it
could be that's an IE 5 problem. Could you try to upgrade your IE 5 or test
it with Netscape?
You can also enable the dbgHeadersIn flag in EMBPERL_DEBUG and take a look
at the embperl logfile. You should see the cookie with the session id for
every request in the http headers your browser send. Are the session id
correctly send by the browser?
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
