Application Performance

in 3-tier Forms applications it is likely that the forms hanged due the period of idle time. If this is the case you can increase the idle time settings. Read the following text:

You are running forms on the web and want the ability to automatically
close a client connection and release the forms web process if a
client remains idle for a particular amount of time. For example, say
you have many users performing data entry and you want to conserve
resources as much as possible. You can implement a five minute maximum
idle time to users, after which their connection is lost and the
ifweb60 process is shut down, which frees resources.

Terminating a User Session Based on Idle Time in Forms 6i
=========================================================
Follow this procedure to terminate a user session based on idle time
in Forms 6i (Forms 6.0.8.8 or higher):

1) Create a registry/environment variable called FORMS60_TIMEOUT.

2) Set FORMS60_TIMEOUT to a value of 5. This parameter specifies the
amount of time in elapsed minutes before the Forms Server process
  is terminated when there is no client communication with the Forms
Server.  The default is 15, and valid values are integers
between 1 - 1440 (1 day.)  For example:

  FORMS60_TIMEOUT=5

3) In your html file, insert a new parameter called heartBeat. This
parameter sets the frequency at which a client sends a packet to
  the server to indicate that it is still running. The default value
is two minutes. Set this parameter value to greater than the value
specified for the FORMS60_TIMEOUT variable. For example, set it to
7 minutes as follows after the serverArgs parameter:

For Internet Explorer:

<PARAM NAME="heartBeat" VALUE="7">

For Netscape Browser:

heartBeat="7"

Now, if a user is idle, (that is, if they do not use their form for
five minutes) the connection is lost and the ifweb60.exe process for
that user is automatically terminated.

Note: When the ifweb60 process is terminated, the client process is
     not notified, and therefore no message is displayed on the
     client side. For the user, it appears that their session is
     hung. The user must close all browser windows to restart the
     application. Please consider this when implementing this
     functionality.

Solution Explanation
====================
The ifweb60.exe timeout depends upon the heartBeat parameter. When a
client is idle, a packet is sent every two minutes to the client and
even though it is idle, it still finds it alive. If the packet finds
the client dead, it terminates the ifweb60 process after 15 minutes
(the default for FORMS60_TIMEOUT.) If you set the value of
FORMS60_TIMEOUT to less than the value of heartBeat, the forms server
does not get a reply from the client within the specified timeout
period and it thinks the client is stopped and terminates the
ifweb60.exe process.