Hi Perrin I removed the manual rollback and let the job to Apache::DBI, the problem is that after the change, the message about the handle destroyed still appears in the log. I activated the $Apache::DBI::DEBUG variable, but the message persist (now with the DEBUG information).
Issuing rollback() for database handle being DESTROY'd without explicit disconnect(). 24833 Apache::DBI new connect to 'dbname=xxxx;host=localhost xxx xxxx AutoCommit=0 PrintError=1 RaiseError=1 Username=xxxx' It looks like it's a postgreSQL specific problem. Hans On Wed, 05 May 2004 14:03:02 -0400, Perrin Harkins wrote > On Wed, 2004-05-05 at 13:01, Hans Poo R. wrote: > > I want to know, if it's necessary to rollback database connections on each > > request arrive with a PerlInitHandler, when using persistent database connections. > > Apache::DBI already does that for you in a cleanup handler. You are > using Apache::DBI, right? > > > The side effect of this manual rollback is that the error_log get filled with > > the message: > > > > Issuing rollback() for database handle being DESTROY'd without explicit > > disconnect() > > That's not normal. You shouldn't be getting anything in your error_log > from doing a rollback. You didn't show your code, so I can't speculate > on what's causing it. > > My advice is to remove your code and just let Apache::DBI do it. > > - Perrin -- 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
