I have a curious problem with PerlEx from ActiveState on my W2008 x64 server. IIS 7 is set up with 10 virtual server and two of these make use of PerlEx. One works perfectly and the other doesn't work at all. Both are set up with their own (32 bit) application
pool, the site that works also has a 64-bit application pool to make queries to Indexing Service work with classic ASP. Each perl script is set up to run in it's own PerlEx interpreter class.
In the site that doesn't work the scripts give a 500 error or just appear to hang when run under PerlEx, they run just fine as a normal Perl CGI. Enabling failed request tracing the error I get is
ModuleName
IsapiModule
Notification
128
HttpStatus
500
HttpReason
Internal Server Error
HttpSubStatus
0
ErrorCode
2147943398
ConfigExceptionInfo
Notification
EXECUTE_REQUEST_HANDLER
ErrorCode
Invalid access to memory location. (0x800703e6)
Where to go from this?
I should add that it used to work. When setting up the server I did load testing one each site in turn with the other sites stopped. This included heavy exercising of the PerlEx scripts with loads 10-100 times greater than what we have today. Everything
worked flawlessly. Then I turned on all sites and let the system go live, replacing the old box. Bang! Nothing works on one of the sites.
The sites, for the curious, are http://econpapers.repec.org (works) and http://logec.repec.org (doesn't work, and it is the site that really would benefit from the PerlEx speed up).
That error code sounds like an access-violation somewhere in PerlEx which is being handled and the error reported - not sure why you are only seeing it one site and not the other - but sounds like time to debug PerlEx.
Anil Ruia
Software Design Engineer
IIS Core Server
Marked as answer by Leo Tang - MSFT on Jul 29, 2009 01:11 AM
SuneK
2 Posts
PerlEx (not) working
Jul 21, 2009 09:59 PM|LINK
I have a curious problem with PerlEx from ActiveState on my W2008 x64 server. IIS 7 is set up with 10 virtual server and two of these make use of PerlEx. One works perfectly and the other doesn't work at all. Both are set up with their own (32 bit) application pool, the site that works also has a 64-bit application pool to make queries to Indexing Service work with classic ASP. Each perl script is set up to run in it's own PerlEx interpreter class.
In the site that doesn't work the scripts give a 500 error or just appear to hang when run under PerlEx, they run just fine as a normal Perl CGI. Enabling failed request tracing the error I get is
Where to go from this?
I should add that it used to work. When setting up the server I did load testing one each site in turn with the other sites stopped. This included heavy exercising of the PerlEx scripts with loads 10-100 times greater than what we have today. Everything worked flawlessly. Then I turned on all sites and let the system go live, replacing the old box. Bang! Nothing works on one of the sites.
The sites, for the curious, are http://econpapers.repec.org (works) and http://logec.repec.org (doesn't work, and it is the site that really would benefit from the PerlEx speed up).
/Sune
500 64-bit 32-bit 0x800703e6 PerlEx
anilr
2343 Posts
Microsoft
Re: PerlEx (not) working
Jul 26, 2009 01:53 PM|LINK
That error code sounds like an access-violation somewhere in PerlEx which is being handled and the error reported - not sure why you are only seeing it one site and not the other - but sounds like time to debug PerlEx.
Software Design Engineer
IIS Core Server