This forum has been moved here:
Helicon Tech Community Forum

ISAPI_Rewrite 3.0 (Forum Locked Forum Locked)
 Helicon Tech : ISAPI_Rewrite 3.0
Subject Topic: Application crash ISAPI_Rewrite.dll (Topic Closed Topic Closed)
Author
Message |
wpub
Newbie


Joined: 10 March 2009
Posts: 9
Posted: 19 March 2009 at 4:59am  

Dear Helicontech Team,

we are using ISAPI-REWRITE Version 3.1.0.61 on our servers under very high traffic.

We defined all rules in the global httpd.conf in the application directory.
We have 7 different virtual hosts in this config file.
Our main focus are redirects and so we are using map files for every virtual host.

Every full hour we ware deploying any new changes of the global httpd.conf and the mapfiles to our liver server.

First we copy the configuration file and second the map files.
We are using this order because we recognized that if we are using a global config file, changed map files will only
be reloaded if the config file will be changed. Is this correct?

The main problem is that after this deploying process and reloading of the config file,
isapi rewrite is crashing with the following error:

Event Type:    Error
Event Source:    Application Error
Event Category:    (100)

Description:
Faulting application w3wp.exe, version 6.0.3790.3959, faulting module ISAPI_Rewrite.dll, version 3.1.0.61, fault address 0x00017dfa.

or

Faulting application w3wp.exe, version 6.0.3790.3959, faulting module ISAPI_Rewrite.dll, version 3.1.0.61, fault address 0x00018bf8.

Another problem is that we are not using any .htaccess files in the web directories, just the main configuration
in combination with the mapfiles. Because of security issues, the iis_wpg has no access to this web directories
and isapi rewrite is showing this error:

Begin watch directory changes failed (xxx): Insufficient permissions. (Access is denied.)

Is there any way to configure isapi rewrite to only watching the main configuration file?
Ho can we change the error level, to not protocolling those errrors?

In summary we have the following questions:

1) What is causing this application crash and how can we prevent this?
2) How can we stop the watch directory changes, if this is causing problems?
3) How can we change the error log level ?
4) What is a stable way of using isapi rewrite under high traffic and different virtual hosts? Maybe it is better to use
single .htaccess files instead of one global configuration file?

Best regards
wpub
Back to Top
 
Anton
Admin Group


Joined: 30 January 2007
Location: Ukraine
Posts: 10519
Posted: 19 March 2009 at 9:13am  

1. Please provide DebugDiag log if possible. Also send your config and mapfiles to support@helicontech.com.
2. Please also put "AllowOverride none" in all virtual hosts and on the global level. This will restrict monitoring for all locations except
installation directory and directories with mapfiles. It's also possible to Deny DirectoryListing permission for those dorectories where
monitoring is not necessary.
3. Set "LogLevel info"
4. It should work just fine in any case and under any load. Distributed .htaccess files are better because they allow to reload only specific
parts of server configuration, not the whole one.



__________________
Regards,
Anton
Back to Top
 
Sergey
Admin Group


Joined: 11 March 2005
Posts: 750
Posted: 23 March 2009 at 12:43pm  

Please download the latest build http://www.helicontech.com/download-isapi_rewrite3.htm

The issue was fixed.
Back to Top
 

Sorry, you can NOT post a reply.
This forum has been locked by a forum administrator.

Printable version Printable version