Not quite sure where to start asking this question, but it might involve mp2/Apache::DBI, so I thought this might be a good start.
I have built a web application using mp2 sitting on top of a postgres DB. I still am working out the kinks with the system, but I am having an interesting problem. I have a Modperl::Registy page that I know has an invalid SQL statement in it. Everything is fine if I don't request the 'bad' page. Once I request that page, DBD::Pg prints out an error to the log and that specific apache server's DB connection is no longer valid (I ran with '-X' to verify this) ... my application usually fails in the authen phase, the first time it tries to access the DB. From running this SQL via a command-line perl script, it looks like some part of DBI 'die's ... does Apache::DBI still cache this connection?
I upgraded all the necessary components of the system this morning to their latest (shown below), just to rule out that possibility, but its still happening. I guess I am tending towards the perl DB chain (Apache::DBI, DBI, DBD::Pg)
It doesn't sound like a mp2 core problem. Have you tried enabling Apache::DBI's debug tracing?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
