G
Guest
It appears that IIS hangs the first time two requests are made for same page
in quick succession. Although it may very well be something else I'm doing
wrong.
I have a page (ViewDocument.aspx) that dynamically generates one or more
image tags. The source attribute of the image tag is another page
(ViewImage.aspx) that simply writes the image data to the response.
When I load ViewDocument.aspx for the first time, everything is fine as long
as it only generates one image tag. I can load it again, generating multiple
image tags, and everything is solid.
However if when I load ViewDocument.aspx the first time, and cause it to
generate multiple image tags, IIS hangs (actually needs to be restarted).
When the error occurs, I see that the ViewImage.aspx constructor is called
twice, but that the Page_Load is never called.
Is it possible that the first request is causing the ViewImage.aspx page to
be compiled and if the second request for that page comes before it's
finished being compiled that the whole thing goes off into the weeds?
Thanks,
Brad
in quick succession. Although it may very well be something else I'm doing
wrong.
I have a page (ViewDocument.aspx) that dynamically generates one or more
image tags. The source attribute of the image tag is another page
(ViewImage.aspx) that simply writes the image data to the response.
When I load ViewDocument.aspx for the first time, everything is fine as long
as it only generates one image tag. I can load it again, generating multiple
image tags, and everything is solid.
However if when I load ViewDocument.aspx the first time, and cause it to
generate multiple image tags, IIS hangs (actually needs to be restarted).
When the error occurs, I see that the ViewImage.aspx constructor is called
twice, but that the Page_Load is never called.
Is it possible that the first request is causing the ViewImage.aspx page to
be compiled and if the second request for that page comes before it's
finished being compiled that the whole thing goes off into the weeds?
Thanks,
Brad