I have the same problem, only not with dbiproxy -- with another simple
Perl RPC server I built on the same modules that dbiproxy is built on.
It must be related to the PlServer (?) stuff, and not DBI directly...
Let me know if you figure out how to fix the problem...
Rob
On Fri, Oct 27, 2000 at 12:36:26PM +0200, Marinos J. Yannikos wrote:
> Has anyone used dbiproxy extensively? I seem to be getting hundreds of
> zombie Perl processes (until the proc table is full) after a while. I only
> replaced my data source string with an equivalent dbi:Proxy:... string and
> started dbiproxy. Is this a known bug, or is there something I should have
> done differently?
>
> I was trying to reduce the number of active postgres client processes
> (Apache::DBI created too many) without while still avoiding the postgres
> connect() overhead. It turned out that the latter was much less severe than
> the performance problems caused by ~ 100 active postgres client processes,
> so I stopped using Apache::DBI. Any other suggestions?
>
> Regards,
> Marinos
> --
> Marinos J. Yannikos
> Preisvergleich Internet Services AG, Linke Wienzeile 4/2/5, A-1060 Wien
> Tel/Fax: (+431) 5811609-52/-55
> ==> Geizhals-Preisvergleich - jetzt auch für Deutschland:
> http://geizhals.cc/de/
--
Rob Fugina, Systems Guy
[EMAIL PROTECTED] -- http://www.geekthing.com
My firewall filters MS Office attachments.
If words could speak, I wonder what they'd say.
