> Sounds like you should have some more code in your finally
> blocks. :)
Well I don't quite like having to do that everywhere, especially in
code I did not write. In Perl I only need one of them using some
AUTOLOAD trickery :-).
--
Dominique QUATRAVAUX Ingénieur dével
Sure. And beware of connections that are returned to the pool without
being rollbacked, too - the app then deadlocks itself because it holds
locks in the database and doesn't know it does. I get bitten by this
under JDBC every so often, when an exception is thrown at the wrong
time.
Sounds like
>
> Well, it's going to be a pretty strange environment that doesn't have a
> database connection in every process.
Sure. And beware of connections that are returned to the pool without
being rollbacked, too - the app then deadlocks itself because it holds
locks in the database and doesn't know
At 9:56 Uhr -0800 23.12.2002, Michael Teter wrote:
Do production, public mod_perl-based sites have 10s or 100s of database
connections open?
Using mod_accel (better than mod_proxy) for a proxying setup you can
keep the number of mod_perl enabled httpd children low, saving both
memory and datab
If I recall correctly, Jeffrey Baker (author of Apache::Session) wrote
an extremely lucid and well thought out argument about why the way
mod_perl pools connections is just as well as Java in reality.
Try searching for his name in the mod_perl list archives.. I think he
wrote this over a year a
Jean-Michel Hiver wrote:
[...]
* I _think_ that mod_perl 2 on Apache 2 might solve your problem since
it's threaded (list, am I right here? I'm still working on mp1 for the
most part)
Eventually, yes.
__
Stas BekmanJAm_
> My understanding is that database access via mod_perl is pooled, but
> only per-httpd. So if I had 10 active httpds running, I would have
> 10x(number of connections per pool).
The number of connection per "pool" (it's really just a cache) is normally
one, so you have one per process. You woul
Not necessarily, that would be your MAXIMUM number of simultaneous
connections, unless you connect to all the datababases when a children
is spawn (which would be pretty dull methinks, I prefer lazy
algorithms).
Well, it's going to be a pretty strange environment that doesn't have a
database
> My understanding is that database access via mod_perl is pooled, but only
> per-httpd. So if I had 10 active httpds running, I would have 10x(number of
> connections per pool).
Not necessarily, that would be your MAXIMUM number of simultaneous
connections, unless you connect to all the datababa
