What may be the reason for the following behavior:
There is an asp.net application. The application is quite complex.
Sometimes user request processing lasts long (even 1 [s]).
When user postbacks some data or enters the page for the first time, his
browser is not freezed. Whenever the user wants, he can stop, refresh or
go somewhere else, whilst the request is being processed.
And the problem now:
When the request is being processed, and the client refreshes his browser
(or requests something else, but still within the same application)
the requests instead of being processed get blocked. It looks as
if the server process has hung, and the browser is waiting for the response.
The response comes after 50-140 [s].
This happens only if user requests something, while his previous request
is still being processed.
What may be the reson for this strange behaviour ?
In my opinion, the server should queue the requests coming from the same
session
and process them. however the machine is idle, nothing happens for 1 minute.
To make things worse, not only _this_ client session freezes. If other guys
use the application, they also wait so long.
To make things even worse, this happens also to other asp.net applications
running in the context of the aspnet_wp.exe. Clients of those web applications
also do wait (only due to the fact that somebody has pressed browser refresh
button too frequently).
Help
Michal
