Last post Sep 11, 2013 12:03 PM by pkloeb
Sep 10, 2013 12:41 PM|pkloeb|LINK
We have a webservice. It calls a stored procedure on a DB2 database. We call it using the BeginMethod/EndMethod as it is an older application. The issue is on long running DB2 stored procedures, once done, will not display back on the .aspx page. Now
let me say that procedures that take 3,4,5 or even 6 minutes display back to the page, but the one that takes 13 minutes does not. All our timeouts have been set to 40 minutes.
The set up is .aspx calls functions in a DAL that calls the Web Service methods. We use an Async Page to do the processing and redirect back to the calling page.
I put some Writes to the Event Log and they ALL write the expected results.
I'm at a loss here on why this works for 1 second to 6 minute calculations, but not for the 13 minute one. ANY and ALL help is appreciated.
BeginAsyncOperation), New EndEventHandler(AddressOf
'//**G's Code End
'Dim wsVSPS As New VSPSDS.ShelfPriceSurveyDS
' AddHandler wsVSPS.calculateSurveyPassFailCompleted, New VSPSDS.calculateSurveyPassFailCompletedEventHandler(AddressOf
'//**K's Code End
'The write to the
log works fine as did the one in the EndAysnc Sub and with the expected results
EventLog.WriteEntry(sEvent,"Now response.redirect back",
EventLogEntryType.Information, 18010, CType(3,
'Anything dealing with the page doesn't not work. Even a texbox.text=the results will not display.
EventLog.WriteEntry(sEvent,"Begin Async Call",
EventLogEntryType.Information, 18001, CType(3,
Return dal.calculateSurveyPassFailAsync(Session("Survey ID"), cb, state)
ar As IAsyncResult)
strResults = dal.calculateSurveyPassFailAsyncEnd(ar)
EventLog.WriteEntry(sEvent,"AysncCalculation.aspx received these results : "
& strResults, EventLogEntryType.Information, 18009, CType(3,
If Left(strResults, 9) =
"Survey calculations were completed successfully for survey : "
& Session("Survey ID")
ElseIf Left(strResults, 7) =
Session("SURVEYCALCREPLY") = strResults
"An unknown error has occured. " & strResults &
" Please contact the help desk."
Sep 11, 2013 02:11 AM|Shiva Ammisetty|LINK
Did you check the executionTimeout setting of httRuntime in your web.config file? Is this entry exist in your web.config? Are the timeouts of you WCF service and Web application are in sync? Ideally this should match as well. Below is an example which set
the time of web reqeust to 15 minutes and this means if any request takes more than 15 mins the IIS will automatically timesout this reqeust and will not serve.
Sep 11, 2013 12:03 PM|pkloeb|LINK
Yes, we have the <httpRuntime executionTimeout="2400"> It's overkill, but just wanted to make sure.
Got any other thoughts...we are at a loss around here.