Attempt to free non-existent shared string during global destruction.
One of the processes no longer uses the object, and wants to destroy it. Here's a piece of documentation on this:
InactiveDestroy (boolean)
This attribute can be used to disable the database engine related effect of DESTROYing a handle (which would normally close a pre- pared statement or disconnect from the database etc).
For a database handle, this attribute does not disable an explicit call to the disconnect method, only the implicit call from DESTROY.
The default value, false, means that a handle will be automatically destroyed when it passes out of scope. A true value disables auto- matic destruction. (Think of the name as meaning 'inactive the DESTROY method'.)
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 on all their shared handles. Note that some databases, including Oracle, don't support passing a database connection across a fork.
- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.
In reply to Re: DBI and fork()
by Juerd
in thread DBI and fork()
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |