What happens to a web forms session that has been terminated by closing the browser and without using the EXIT buttons etc coded inside the application?
We have forms sessions which perform two kinds of updates
- Base Table updates
- Directly execute DML into the database by stored procs
What happens in either case if after some changes are made the user closes the browser?
I have found that when DML is executed and the browser is closed or crashes, and if the user opens another browser and tries to amend the same set of data, the second sessions waits on the locks which are not yet released by the first session.
What is a fool proof way to get around applications from hanging by waiting on such locks?
How can an exit from the browser be prevented?
How can cleanup action/rollbacks etc be done in forms when the browser is closed? How can forms detect it in the first place?
I am aware of the FORMS60_TIMEOUT but don't think this is good enough since we can't set it to too less a time and if we don't then there is a possibility that the user may open another session quicly and wait on the unreleased locks from his previous session which is still not terminated