As you know the disconnect-method does not work with Apache::DBI. From the docs:
There is no need to remove the disconnect statements from your code. They won't do anything because the Apache::DBI module overloads the disconnect method.
Also the docs of Apache::DBI warn against opening too many connections which can easily happen:
The Apache::DBI module still has a limitation: it keeps database connections persistent on a per process basis. The problem is, if a user accesses several times a database, the http requests will be handled very likely by different servers. Every server needs to do its own connect. It would be nice, if all servers could share the database handles. Currently this is not possible, because of the distinct name-space of every process. Also it is not possible to create a database handle upon startup of the httpd and then inheriting this handle to every subsequent server. This will cause clashes when the handle is used by two processes at the same time.With this limitation in mind, there are scenarios, where the usage of Apache::DBI is depreciated. Think about a heavy loaded Web-site where every user connects to the database with a unique userid. Every server would create many database handles each of which spawning a new backend process. In a short time this would kill the web server.
The strange thing is that it happens also without using Apache::DBI. Are you sure that Apache::DBI is not started "silently" in the background by mod_perl's configuration?
CountZero
"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
In reply to Re: CGI::Application not disconnecting from the database?
by CountZero
in thread CGI::Application not disconnecting from the database?
by jgallagher
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |