in reply to Re: Creating new database handles with mod_perl
in thread Creating new database handles with mod_perl

I've read each of those cover to cover many times. I'm a long time Perl user: not quite a Monk but getting there.

The one thing I am missing conceptually is how to verify that 2 child processes indeed have a different connection. Both $dbh have the same memory address, but does that mean a shared connection? Maybe, maybe not, since the addresses are virtual.

I've been using Apache2::Status heavily, and documentation states that there is a section on handles, but it's not showing up for me and I haven't debugged why yet. If that would answer whether handles shared or not, maybe I should focus on debugging why the handles are not showing up in Apache2::Status.

  • Comment on Re^2: Creating new database handles with mod_perl

Replies are listed 'Best First'.
Re^3: Creating new database handles with mod_perl
by Anonymous Monk on May 22, 2012 at 09:14 UTC

    I've read each of those cover to cover many times. I'm a long time Perl user: not quite a Monk but getting there.

    :D Just covering my bases :)

    The one thing I am missing conceptually is how to verify that 2 child processes indeed have a different connection. Both $dbh have the same memory address, but does that mean a shared connection? Maybe, maybe not, since the addresses are virtual.

    My ideas for verification were checking the logs, or database server status. Are you sure you're not watching the same child? Are you checking the pid $$? $Apache::DBI::DEBUG=2 enables debugging output with pids :)

    Same memory address does not mean shared connection, each process gets a "distinct memory-space", but I would be surprised if both children would happen to have the same address. I suppose it might happen theoretically, but I doubt it :)

    maybe I should focus on debugging why the handles are not showing up in Apache2::Status.

    I don't see mention of handles in Apache2::Status docs, what handles are you talking about?