I have a legacy Perl application that I would like to deploy using 
PerlEx. For reasons beyond my control at the moment, it uses and leaks 
memory like crazy.

I had hoped to deal with this by taking advantage of worker process 
recycling in the application pool, but as reported by others, this 
doesn't work very well.

a) with multiple worker processes, the web application very quickly 
hangs forever. IIS seems to be unable to restart the worker processes
b) with a single worker process, it can run for a few hours. However, 
when virtual memory usage is high for the worker process, requests take 
several minutes to service. Neither IIS nor the browser time out on 
these requests. After a few hours, IIS completely hangs again and 
doesn't automatically restart. Clearly this is unacceptable -  missed 
response or two might be okay, but the application has to be able to 
restart.

Other messages to the ActiveState forums have suggested that installing 
service pack 2 would solve similar problems, but this does not seem to 
be the case.

Does anyone have any further insight into this situation? Isn't it 
really strange that IIS can't restart its worker processes?

Any help would be greatly appreciated.


--------------------- Perl Version -------------------------------
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 33 registered patches, see perl -V for more detail)

Copyright 1987-2006, Larry Wall

Binary build 819 [267479] provided by ActiveState http://www.ActiveState.com
Built Aug 29 2006 12:42:41

-- 

Bryan M. Kramer
Email: bryan.kramer@[...].com <mailto:kramer@[...].com> 
_______________________________________________
ActivePerl mailing list
ActivePerl@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs