Re: Problems with the embperl caching mechanism

[Gerald Richter <ri...@ecos.de>]

Hi,

Embperl does _no_ database connection cacheing at all. Maybe your database
module holds the connection in a global variable, which will persist between
multiple request under mod_perl, but this is a general mod_perl issue and
has nothing to do with Embperl's caching. A good starting point for
searching about such issues is the mod_perl guide under perl.apache.org.

Without more details I can't say much more.

Gerald

P.S. The right place to ask such questions is the Embperl mailing list, so
other people can participate

-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de         Voice:    +49 6133 925131
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------

----- Original Message -----
From: "Bernd Friedrich" <sp...@t-online.de>
To: <ri...@ecos.de>
Cc: <be...@spidersoft.de>; <al...@spidersoft.de>
Sent: Thursday, June 14, 2001 12:17 PM
Subject: Problems with the embperl caching mechanism


>
> Hello Mr. Richter,
>
> we use embperl in two of our dynamic web sites and have the following
> problem:
>
> We connect to two Postgres Databases and use for the two sites the same
> perl database module.
>
> If the first site connects to the database, the connection string is OK,
> the
> site works fine. If the second site tries to connect to the database, it
> get's
> the connection of the first site !!!
>
> I think, the problem here is the caching mechanism of embperl, it seems
> for
> me, that our perl database module is loaded once and this module is used
>
> forever.
>
> When I restart our web-server, then the second site uses it's database
> connection
> and everything works fine for the second site. The problem has now the
> first
> site which get's the connection string of the second site.
>
> My question is:
> Is there any possibility to force the embperl not to cache our database
> module ???
>
> Or
>
> Could you imagine a workaround on that problem ???
>
>
> Thanks and Regards
> Bernd Friedrich
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org