I just ran into some very strange issues with connections to a PostgreSQL database (using DBD::Pg) getting unceremoniously dropped by my web application. I was getting error messages such as these:
[Tue Jul 22 13:21:44 2003] [error] [client 207.172.11.148] Unable to turn AutoCommit off: DBD driver has not implemented the AutoCommit attribute at /usr/local/lib/perl5/site_perl/5.8.0/Bric/Util/DBI.pm line 528, <GEN71> line 57.
Database handle destroyed without explicit disconnect at /usr/local/lib/perl5/site_perl/5.8.0/Bric/Util/DBI.pm line 1661.
Database handle destroyed without explicit disconnect at /usr/local/lib/perl5/site_perl/5.8.0/Bric/Util/DBI.pm line 1661.
commit ineffective with AutoCommit enabled at /usr/local/lib/perl5/site_perl/5.8.0/Bric/Util/DBI.pm line 571.
Database handle destroyed without explicit disconnect at /usr/local/lib/perl5/site_perl/5.8.0/Bric/Util/DBI.pm line 1661.
The PostgreSQL log had these errors:
FATAL: Socket command type H unknown FATAL: Socket command type 0 unknown LOG: pq_flush: send() failed: Broken pipe
After a great deal of experimentation and recompilation, I finally identified Apache 1.3.28 as the culprit. When I reverted to 1.3.27, the problem went away.
Now, I'm going to take this problem up with the mod_perl and Apache folks, but I also wanted to enquire here to see if others were running into this problem with their mod_perl applications connecting to databases other than PostgreSQL. I duplicated the problem on FreeBSD and on Mac OS X, and I had a report of the problem on Solaris, so I'm reasonably sure it's not an OS issue. If anyone has this type of problem with other databases, then we can likely eliminate DBI or DBD::Pg as being part of the problem.
Many thanks,
David
-- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://kineticode.com/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
