Last post Jul 01, 2010 04:01 PM by whighfield
Jul 01, 2010 02:41 PM|tjgervaisasp|LINK
I am executing a long-running Oracle stored procedure from .NET. The procedure takes about three hours to run. Ideally, the user should be able to kick off the procedure, close the browser, and come back later to check the results.
The problem is that the connection to the Oracle procedure is lost after exactly an hour. As you would expect, the Oracle procedre runs to completion if it is executed from SQL Plus. Strangely enough, it will also run to completion if I run in debug mode
on my local machine (I start two threads, one of which executes the procedure. I set a breakpoint on the second thread).
Here is my connection string:
data source= (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=serverx)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=TestSID)))
Some relevant sections from web.config:
<sessionState mode="InProc" cookieless="false" timeout="3000" stateNetworkTimeout="72000"/>
<httpRuntime executionTimeout="18000" maxRequestLength="2097151" />
Any thoughts as to why the connection is being lost in exactly an hour, and what I can do to maintain the connection until the procedure finishes?
Jul 01, 2010 04:01 PM|whighfield|LINK
Not an answer but more of a question what happens if 5 people open up the same page and kick off this process? Or better yet the same user clicks on the process button 5 times? Is there a constraint to only allow one process to be kicked off an any given
How about service the process out so that it happens nightly rather than by a user? If it takes 3 hours really then the user can only run it twice a day anyway.
Just some thoughts..