I actually did something like that, but when I did, the browser would return the html, the http headers and all to the browser so that the page would not be rendered. Instead of the string that I tried to output in the destroy method, I would get '0' after the </html>.
On 10/10/06, Dondi M. Stroma <[EMAIL PROTECTED]> wrote:
If I were you, I would put something like warn "I'm being destroyed."; in the DESTROY method, so you'll know for sure whether that is the case. ----- Original Message ----- From: "Jordan McLain" <[EMAIL PROTECTED]> To: <modperl@perl.apache.org> Sent: Tuesday, October 10, 2006 11:20 PM Subject: Re: Re: Re: DESTROY > That is not the problem... The problem comes in when I do not use > Apache::DBI and I still end up with alot of mysql threads. The > problem is that I do not think DESTROY is being called. > > On 10/10/06, Jordan McLain <[EMAIL PROTECTED]> wrote: >> That is not the problem... The problem comes in when I do not use >> Apache::DBI and I still end up with alot of mysql threads. The >> problem is that I do not think DESTROY is being called. >> >> On 10/10/06, Jeff Pang <[EMAIL PROTECTED]> wrote: >> > >> > >> > > >> > >I am not sure, but I think the problem you have is that Apache::DBI >> > >ignores >> > >any disconnect() calls on database handles, and doesn't actually >> > >disconnect. >> > >> > >> > That's true.Apache::DBI ignores all the disconnect() calls. >> > >> > -- >> > Jeff Pang >> > NetEase AntiSpam Team >> > http://corp.netease.com >> > >>
