Hi Rob,
Thanks for your updated information about the IIS isolation mode.
When you configure IIS 6.0 to run in IIS 5.0 isolation mode, ASP.NET runs
in its own process model, Aspnet_wp.exe, and uses its own configuration
settings. These settings are stored in the computer-wide Machine.config
configuration file.
When running on IIS 6.0 in worker process isolation mode, ASP.NET uses the
IIS 6.0 process model settings.
#Mapping ASP.NET Process Model Settings to IIS 6.0 Application Pool Settings
http://msdn2.microsoft.com/en-us/lib...66(VS.71).aspx
For the IHttpModule.Init issue, I've also found some updated information:
#INFO: Application Instances, Application Events, and Application State in
ASP.NET
http://support.microsoft.com/kb/312607
<quote>
The ASP.NET runtime creates as many instances of application classes as
needed to process requests simultaneously. For most applications, this
number is limited to the number of threads and remains in the range of 1
through 100, depending on the hardware, server load, configuration, and so
on. Many requests reuse application instances, and a free list of
application instances is kept during periods of reduced load. Application
instances are used in a thread-safe manner, that is, one request at a time.
</quote>
Sorry for not clarifying this fact in my last reply.
Based on these information, my guess is that your IIS 6.0 application pool
settings are causing each request using a new HttpApplication instance.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
