Timeout calling webservice
I have an intranet application that is calling a webservice (code below). The webservice calls a stored procedure in q sql server 2005 that again does an openquery on a db2 (AS400) machine. The stored procedure is returning a temp table.
On the call to the webservice I am getting a time out. At this point if time out the web service is still running and I can also see the query is in the program stack on the db2 machine. The query itself can take up to 20-30 minutes as it is reading 3 mill+ records. If I call the web service directly I get the result returned.
Code:
Dim getOrderDetail As New localhost.OrderDetail
myDataTable = getOrderDetail.GetOrderDetailRecords_DataTable(myUserId)
Is there a timeout setting I need to look at or any other suggestion? Thank you.
Re: Timeout calling webservice
Hi.There is a session timeout at web.config: http://msdn.microsoft.com/en-us/libr...8vs.80%29.aspx
There is also a session timeout in IIS: http://technet.microsoft.com/en-us/l...=ws.10%29.aspx
IN IIS 7 i find it under "yoursite" - session state.
Re: Timeout calling webservice
Your web request from the browser is not going to want to wait 30 minutes for a sproc to complete on the server.
Sapator - correct me if I am wrong - but 30 minutes seems beyond the scope of what a post/response is going to wait for...
imo - you are going to have to re-think the method of deliverying this content.
Re: Timeout calling webservice
Missed the 30 minutes part!No you are not wrong.These problems will be caused by poor design and i had a same issue on a big insurance company that i had worked with, so even big fat companies make such mistakes.
Re: Timeout calling webservice
Quote:
Originally Posted by
szlamany
Sapator - correct me if I am wrong - but 30 minutes seems beyond the scope of what a post/response is going to wait for...
You can extend the time that the Web Server will wait for a response, but waiting anything longer than a couple minutes, in this day and age, would seem inappropriate.
Gary
Re: Timeout calling webservice
I wonder what the OP has done with this issue.
Openquery calls to mainframe databases can be painfully slow.
I would see if I could cache the openquery results locally somehow - and then worry about "how fresh the data is"
- or even create my own agent on the mainframe to get the data in a more "quick" fashion - if that's even possible.