IIS Stuck in SendResponse state
up vote
1
down vote
favorite
I have a classic VB6 ASP application compiled into dll's and executed through COM. The web site pulls from a SQLServer database.
One particular function builds a page by getting data rows, and then for each data row queries the database again to build rows in a sub table.
The problem is that if this page is large, and if the request for the page comes from a remote machine, then the IIS server gets stuck in the SendResponse state and never sends the page. If I call that same page using the same dataset, but call it from a browser running on the server itself, the page is quickly built and rendered. If I modify the sqlquery so that fewer rows are returned and the page is smaller, all clients can quickly load and render
I think I've confirmed that even when the page hangs the sql queries complete quickly and the COM objects have completed building the page.
I have a test server where I can test exact copies of the application but I haven't been able to find a setting in IIS or the apps web.config files that will duplicate the issue.
Is there something at the OS network layer I should be checking?
asp-classic com iis-7.5 windows-server-2008-r2
asked Aug 27 '15 at 20:47
Bill Hurt
447418
add a comment |
up vote
1
down vote
favorite
I have a classic VB6 ASP application compiled into dll's and executed through COM. The web site pulls from a SQLServer database.
One particular function builds a page by getting data rows, and then for each data row queries the database again to build rows in a sub table.
The problem is that if this page is large, and if the request for the page comes from a remote machine, then the IIS server gets stuck in the SendResponse state and never sends the page. If I call that same page using the same dataset, but call it from a browser running on the server itself, the page is quickly built and rendered. If I modify the sqlquery so that fewer rows are returned and the page is smaller, all clients can quickly load and render
I think I've confirmed that even when the page hangs the sql queries complete quickly and the COM objects have completed building the page.
I have a test server where I can test exact copies of the application but I haven't been able to find a setting in IIS or the apps web.config files that will duplicate the issue.
Is there something at the OS network layer I should be checking?
asp-classic com iis-7.5 windows-server-2008-r2
asked Aug 27 '15 at 20:47
Bill Hurt
447418
Why doing a query for each result? This may be a buffer limit issue. Try to addresponse.flushor increase buffer size. There a lot of post on this, like this one : stackoverflow.com/questions/4968006/…
– DanB
Nov 12 at 14:06
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a classic VB6 ASP application compiled into dll's and executed through COM. The web site pulls from a SQLServer database.
One particular function builds a page by getting data rows, and then for each data row queries the database again to build rows in a sub table.
The problem is that if this page is large, and if the request for the page comes from a remote machine, then the IIS server gets stuck in the SendResponse state and never sends the page. If I call that same page using the same dataset, but call it from a browser running on the server itself, the page is quickly built and rendered. If I modify the sqlquery so that fewer rows are returned and the page is smaller, all clients can quickly load and render
I think I've confirmed that even when the page hangs the sql queries complete quickly and the COM objects have completed building the page.
I have a test server where I can test exact copies of the application but I haven't been able to find a setting in IIS or the apps web.config files that will duplicate the issue.
Is there something at the OS network layer I should be checking?
asp-classic com iis-7.5 windows-server-2008-r2
asked Aug 27 '15 at 20:47
Bill Hurt
447418
I have a classic VB6 ASP application compiled into dll's and executed through COM. The web site pulls from a SQLServer database.
One particular function builds a page by getting data rows, and then for each data row queries the database again to build rows in a sub table.
The problem is that if this page is large, and if the request for the page comes from a remote machine, then the IIS server gets stuck in the SendResponse state and never sends the page. If I call that same page using the same dataset, but call it from a browser running on the server itself, the page is quickly built and rendered. If I modify the sqlquery so that fewer rows are returned and the page is smaller, all clients can quickly load and render
I think I've confirmed that even when the page hangs the sql queries complete quickly and the COM objects have completed building the page.
I have a test server where I can test exact copies of the application but I haven't been able to find a setting in IIS or the apps web.config files that will duplicate the issue.
Is there something at the OS network layer I should be checking?
asp-classic com iis-7.5 windows-server-2008-r2
asp-classic com iis-7.5 windows-server-2008-r2
asked Aug 27 '15 at 20:47
Bill Hurt
447418
asked Aug 27 '15 at 20:47
Bill Hurt
447418
asked Aug 27 '15 at 20:47
Bill Hurt
447418
asked Aug 27 '15 at 20:47
Bill Hurt
447418
asked Aug 27 '15 at 20:47
Bill Hurt
447418
447418
Why doing a query for each result? This may be a buffer limit issue. Try to addresponse.flushor increase buffer size. There a lot of post on this, like this one : stackoverflow.com/questions/4968006/…
– DanB
Nov 12 at 14:06
add a comment |
Why doing a query for each result? This may be a buffer limit issue. Try to addresponse.flushor increase buffer size. There a lot of post on this, like this one : stackoverflow.com/questions/4968006/…
– DanB
Nov 12 at 14:06
Why doing a query for each result? This may be a buffer limit issue. Try to add
response.flush or increase buffer size. There a lot of post on this, like this one : stackoverflow.com/questions/4968006/…– DanB
Nov 12 at 14:06
Why doing a query for each result? This may be a buffer limit issue. Try to add
response.flush or increase buffer size. There a lot of post on this, like this one : stackoverflow.com/questions/4968006/…– DanB
Nov 12 at 14:06
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32259155%2fiis-stuck-in-sendresponse-state%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why doing a query for each result? This may be a buffer limit issue. Try to add
response.flushor increase buffer size. There a lot of post on this, like this one : stackoverflow.com/questions/4968006/…– DanB
Nov 12 at 14:06