Lev Lvovsky wrote:
we're trying to simulate a database outage for an application which
needs to be able to fail gracefully, and come back up when the DB does.
These errors can also be seen when the mysql server is restarted
(connections get killed then too).
Yes, in both cases you no longer
Lev Lvovsky wrote:
Once you reconnect, the connection is persistent again. At least,
that's been my experience with postgresql.
This is exactly what I've been thinking to do, but I've not seen
anything within Apache::DBI that allows me to reconnect per se. How do
I perform that action?
Al
I forgot to mention also that we're not using a startup.pl file, but
instead connecting to the DB several times using several different
accounts as a specific virtual host requires. At the risk of
pointing out the answer for myself, does this adversely affect anything?
thanks,
-lev
On Nov
On Nov 28, 2006, at 3:04 PM, Robert Landrum wrote:
Lev Lvovsky wrote:
In testing out persistent connections while using transactions,
we've noticed that while in a loop which continuously begins and
ends a transaction, killing the persistent connection which
Apache::DBI is maintaining ca
Lev Lvovsky wrote:
In testing out persistent connections while using transactions, we've
noticed that while in a loop which continuously begins and ends a
transaction, killing the persistent connection which Apache::DBI is
maintaining causes the still-running handler to report things like:
erro
On Nov 27, 2006, at 11:16 PM, Philip M. Gollucci wrote:
In testing out persistent connections while using transactions,
we've noticed that while in a loop which continuously begins and
ends a transaction, killing the persistent connection which
Apache::DBI is maintaining causes the still-r
On Nov 28, 2006, at 6:18 AM, Perrin Harkins wrote:
/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/DBI.pm line
1668.
That's what it says when you're trying to do something to a $dbh
that is not connected. Why are you killing the connection during a
transaction? What are you trying
Lev Lvovsky wrote:
In testing out persistent connections while using transactions, we've
noticed that while in a loop which continuously begins and ends a
transaction, killing the persistent connection which Apache::DBI is
maintaining causes the still-running handler to report things like:
er
Lev Lvovsky wrote:
perl-Apache-DBI-1.01-1
This is new enough to include the 2 changes I listed below from its
Changes file; however, I'd recommend v1.06
perl-DBI-1.52-1.fc5
perl-DBD-mysql-3.0008_1-1
MySQL 5.022 for all mysql related RPMs
These are fine.
Seems like your Apache::DBI::ping() met
Hi Philip,
On Nov 27, 2006, at 11:16 PM, Philip M. Gollucci wrote:
Lev Lvovsky wrote:
Hello - this may be a question unrelated to mod_perl so much as it
is related to DBI and mysql, but any suggestions would be
appreciated greatly!
What versions of Apache-DBI, DBI, mysql ?
perl-Apache-DB
Lev Lvovsky wrote:
Hello - this may be a question unrelated to mod_perl so much as it is
related to DBI and mysql, but any suggestions would be appreciated greatly!
What versions of Apache-DBI, DBI, mysql ?
In testing out persistent connections while using transactions, we've
noticed that whi
Hello - this may be a question unrelated to mod_perl so much as it is
related to DBI and mysql, but any suggestions would be appreciated
greatly!
In testing out persistent connections while using transactions, we've
noticed that while in a loop which continuously begins and ends a
transac
12 matches
Mail list logo
