Note what the DBI documentation has to say about InactiveDestroy (emphasis mine):
This attribute is specifically designed for use in Unix applications that "fork" child processes. Either the parent or the child process, but not both, should set InactiveDestroy true on all their shared handles. (Note that some databases, including Oracle, don't support passing a database connection across a fork.)
You do set InavtiveDestroy unconditionally. Also, you don't show where you call fork() and you don't tell us what database you use. I think that properly using InactiveDestroy, as per the documentation, should fix this problem, but if you continue having problems, a small, self-contained example will likely elicit better answers than mine.
In reply to Re: The pain of DBI !!! Lost connection from forked or threaded children
by Corion
in thread The pain of DBI !!! Lost connection from forked or threaded children
by expresspotato
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |