I have a problem where asynchronous thread behaves differently based on the time.

When user clicks a button, application starts a report
process in an asynchronous thread. The user gets the
control back on the ASP page so that s/he can continue
other work.

The thread does following steps:
1. Invokes a ORACLE stored procedure #1.
2. Invokes a ORACLE stored procedure #2.
3. Invokes a ORACLE stored procedure #3.
4. Loops through the output and inserts in other dependant
tables.
5. Prints the reports.

When the user comes back to the screen which launched the
report, it can see the status. If complete, report can be
opened.

Step#1 takes 1.5hrs (when run after business hours) to
6hrs (when run during business hours). The problem is
during business hours, the thread does not execute step#2
through step#5 (I have waited entire weekends!). It just
vanishes. If run in debug mode, the execution bar remains
on call to stored procedure.

I know for sure that stored procedure in step #1 is
working because I can track and follow the status through
SQL*Plus.

All the process model parameters are INFINITE wherever
applicable. Any leads will be appreciated. Does anybody think garbage collector is messing? Note that when I break debug mode after 6-18 hrs in VB.NET IDE, it displays message in the output window indicating that thread was able to reconnect to my web server.

Please let me know if you need additional details.



Hozi.
.