Sign In| Join
Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 20, 2009 07:12 AM by charly.p
Member
348 Points
305 Posts
Oct 19, 2009 09:06 AM|LINK
I have a big transaction going on when a user clicks a button, 10.000 lines parsed and max 2 minutes to wait the processing.
Now what happens when de user closes the browser ore pushes the back button thinking it is not working ?
As my inserts are in transaction will the code run to the commit point or will this not happen and no rows will be inserted ?
Note: Currently I have no way of speeding up this process.
Kind regards,
Contributor
4879 Points
1257 Posts
Oct 19, 2009 01:24 PM|LINK
my friend use Background Thread..
even if user press the close button..
the operation takes place behind the scene.
hope that helps
All-Star
41134 Points
6022 Posts
Oct 19, 2009 02:39 PM|LINK
charly.p Now what happens when de user closes the browser ore pushes the back button thinking it is not working ? As my inserts are in transaction will the code run to the commit point or will this not happen and no rows will be inserted ?
Generally you don't want any long running processes in the ASP.NET because of worker process recycle. Check Multithreading in ASP.NET or BackGroundWorker thread
Oct 20, 2009 07:12 AM|LINK
I'll check those links.
From my testing I found out that if a user closes his browser during the process the process is not killed on the server, the database commit is done. So no rollback processed.
charly.p
Member
348 Points
305 Posts
On session or when user closes browser rollback a transaction
Oct 19, 2009 09:06 AM|LINK
I have a big transaction going on when a user clicks a button, 10.000 lines parsed and max 2 minutes to wait the processing.
Now what happens when de user closes the browser ore pushes the back button thinking it is not working ?
As my inserts are in transaction will the code run to the commit point or will this not happen and no rows will be inserted ?
Note: Currently I have no way of speeding up this process.
Kind regards,
ashish-1983
Contributor
4879 Points
1257 Posts
Re: On session or when user closes browser rollback a transaction
Oct 19, 2009 01:24 PM|LINK
my friend use Background Thread..
even if user press the close button..
the operation takes place behind the scene.
hope that helps
Gridview
Jquery
Asp.net
Fun !
budugu
All-Star
41134 Points
6022 Posts
Re: On session or when user closes browser rollback a transaction
Oct 19, 2009 02:39 PM|LINK
Generally you don't want any long running processes in the ASP.NET because of worker process recycle. Check Multithreading in ASP.NET or BackGroundWorker thread
"Don't be afraid to be wrong; otherwise you'll never be right."
charly.p
Member
348 Points
305 Posts
Re: On session or when user closes browser rollback a transaction
Oct 20, 2009 07:12 AM|LINK
I'll check those links.
From my testing I found out that if a user closes his browser during the process the process is not killed on the server, the database commit is done. So no rollback processed.