Hello, Yesterday we noticed two things happening about the same time with a mod-perl driven website we managed, and I'm trying to figure out and if how they were related.
On the front end web server machine, the CPU spiked up well beyond average and stayed there. On the backend PostgreSQL 7.4 server, we saw a number or errors that that the number of max connections had been exceeded. Not surprisingly, this resulted in user visible errors on the web server. I'm curious: What is the expected behavior from Apache::DBI in this case? Would it quickly give up and move on, or perhaps continuously ping the database server and wait, creating a high CPU load in the Perl process? Mark