Topic: Vintage custom perl modules hanging in Apache 2.2.16

[ccappa]

I inherited an intranet that runs on a Windows Server 2008, Apache 2.0.64, Active Perl 5.6.0 environment. Someone in 2000 had written custom perl modules to hit our proprietary database and supply the intranet with data. I wanted to add an intranet that hit our SQL Server, so I built on a separate Windows Server 2003 box an Apache 2.2.16, Strawberry Perl 5.12, SQL Server 2005 intranet.
I have been trying to get this SQL intranet to work with the old custom Perl modules and my test cgi keeps hanging when I run it through Apache, but solves correctly when run through the command line. I have debugged it to the point where I know that it hangs when the Perl Win32::API module blesses the new database object and tries to return it to the custom database module. I have tried to put in all of the STDERR fixes I have read online and they have not helped. Does anybody have any ideas?

The custom perl module starts like this:
package Prop::Database
use Win32::API;
use Carp;
my $OpenTopic = new Win32::API("abcde32","OpenTopic",[P, P],N);

and continues until it dies around:
$lpTopic = pack("L",0);
$Topic = pack("a64",$topic);
$return = $OpenTopic->Call($Topic, $lpTopic);

at this point it goes to Win32::API module and never returns. In the apache error log it reads the old "(70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed". This script solves and runs in a second from the command line. Thanks in advance for any thoughts!

[Steffen]

Better to ask the https://perl.apache.org/maillist/modperl.html