This all works fine to disconnect users when the leave for the day with forms still open.
We have a problem where the PC/Browser crashes and leaves the associated Forms Server and Database Sessions open till the 60 minute timout occurrs. In some cases, the user will have Database rows locked for edit. When the user goes back in, they get new sessions on the Forms Server and Database. Being a good user, they try to update the same DB Rows and get stuck behind the previous lock. They call us and we cleanup the sessions.
I would like to have a scenario like this is possible.
Heartbeat kills Forms Sessions at Forms Server if the pc/browser crashes after 3-5 minutes.
forms_timout/session-timeout kills Forms Session at Forms Server after 60-75 minutes if they go home with forms still running.
Anyone know how to do this? Form what I understand, heartbeat set less than forms_timout/session-timeout makes it never timout.
I've read up on using the bean timer, but I 'think' our design makes that inpractical. Users may have several forms open in the browser (single session) and the timer is per form and would kill just the forms and not the Forms Session at Forms Server - do I have this wrong?
After 2 minutes, clients will receive FRM-92102. And no errors will be shown in
the default-web-access.log or in the application.log,
HTTP Server Timeout:
When attempting to run a query in forms that is running longer than 5 minutes,
the following error occurs: FRM-92101
1. Log into Enterprise Manger
2. Connect to the middle tier
3. Click on HTTP Server > Administration > Server_Properties->
4. Change the parameter "Request Timeout" to a number greater than the
default (300 seconds).
Getting a Timeout running reports, and after the report returned a ORA-3114 and
disconnect with forms.
The solution ended up being to set the DCD timer on the Database side. This
entails setting the following line in the sqlnet.ora file (Database side only):
SQLNET.EXPIRE_TIME = 10