User requests serialize when you test your Active Server Pages (ASP) pages from one instance of a browser.
-or-
In Performance Monitor, you see the number of Requests Queued go up even though Requests Executing is less than the number of available threads for ASP, when you test your ASP pages by refreshing a browser.
User requests from the same session are serialized by ASP.
Testing concurrency issues should be done using a stress simulation tool. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
231282Â
(http://kbalertz.com/Feedback.aspx?kbNumber=231282/EN-US/
)
INFO: Stress Tools to Test Your Web Server
You can either disable session state for ASP at the server-side, or you can force new sessions from the client-side. Forcing new sessions at the client-side causes ASP to treat each request to be handled as a separate user session.
For additional information on disabling ASP sessions at the server-side, click the article number below
to view the article in the Microsoft Knowledge Base:
244465Â
(http://kbalertz.com/Feedback.aspx?kbNumber=244465/EN-US/
)
Disable ASP Session State
To force new sessions from the client-side, you need to do the following:
Additionally, if you are using Internet Explorer 4.0, do the following:
- Set the option Browse in New Process.
- Do not launch additional browser windows from within Internet Explorer by clicking New from the File menu, and then clicking Window.
- Do not launch additional browsers windows through client-side script.
This behavior is by design.
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
216580Â
(http://kbalertz.com/Feedback.aspx?kbNumber=216580/EN-US/
)
PRB: Blocking/Serialization When Using InProc Component (DLL) from ASP