Understanding Oracle Forms timeout parameters (or should I say FORMS_TIMEOUT) FRM-92102 – A network error has occurred

Why does my Oracle Form keep randomly disconnecting?

Today I was at a client who was having trouble as their forms were disconnecting randomly after 15 minutes. They tried to play around with the TIMEOUT settings but they got bogged down in too many documents that pointed to more documents. Therefore, I decided to post a quick guide to Oracle Forms timeout parameters. 

The purpose is to help the community configure Forms sessions to time out after a specified period of user inactivity. Here I discuss the specific timeout parameters of Oracle Forms. For general webserver timeout parameters you should look at note  294749.1  on Oracle Support – Troubleshooting WebForms Tuning / Performance /Time out Problems

Oracle Forms 10g relies on 3 settings to control inactivity timeout:

    1) FORMS_TIMEOUT environment variable.

    2) HeartBeat applet parameter.

    3)The session-timeout parameter of the forms servlet in the web.xml configuration file.

1) FORMS_TIMEOUT environment variable:

This is an environment variable that is set in the .env file found $ORACLE_HOME/forms/server/default.env. The default is set to use a file called default.env file but this can be customized in the formsweb.cfg found in $ORACLE_HOME/forms/server/formsweb.cfg  to use .env files for each configuration in which case these should be modified instead of default.env.

Please note: The Forms environment variable FORMS_TIMEOUT is referred to as FORMS90_TIMEOUT in version IAS 9i and 10g R1 (9.0.4) it is in OAS 10g R2 ( it is FORMS_TIMEOUT.

Add a row to the end of the file such as:


The default value for forms timeout is 15 and Valid Values range from  3 to 1440 (1 day).

This parameter specifies the amount of time in elapsed minutes before the Form Services process is terminated when there is no client communication with the Form Services. Client communication can come from the user doing some work, or from the Forms Client heartbeat if the user is not actively using the form.

2) HeartBeat applet parameter:

The HeartBeat parameter is a feature of the applet and it is set in the formsweb.cfg file found in $ORACLE_HOME/forms/server/formsweb.cfg .

This parameter is used to set the frequency at which a client sends a packet to the server to indicate that it is still running. We can define this integer value in minutes or infractions of minutes, for example, 0.5 for 30 seconds. The default is two minutes.

Please note: If the heartbeat is less than FORMS_TIMEOUT, the user’s session will be kept alive, even if they are not actively using the form. HeartBeat is recommended to be at least 2 beats smaller than FORMS_TIMEOUT

In the formweb.cfg file add the following line to the configuration of your choice:


The default value for HeartBeat is 2 and Valid Values range from  1 to 1440 (1 day)

3)The session-timeout  parameter of the forms servlet in the web.xml configuration file:

This file defines the OC4J forms & listener servlet definitions, including servlet parameters and session configuration. The file is found

The value of session-timeout refers to the maximum amount of inactivity that a single session can have before it is automatically invalidated by the server.

Please note: The value of should be the same as FORMS_TIMEOUT.

The following lines must be added to web.xml.



networkRetries applet parameter

Besides the above timeout parameters, there are additional reasons that forms maybe disconnecting that are not timeout based but network related. Usually they are prefaced by error FRM-92102: A network error has occurred. The Forms Client has attempted to reestablish its connection to the Server 5  time(s) without success.  This parameter specifies the number of times the Forms client should try reconnecting to the middle-tier before finally timing out. The Oracle Forms network connection to the server is a little picky as it does not like being ignored. So as such if it tries to reach the server more than 5 times without response it dies. Although this would seem logical most of the time 5 seconds is just too little if we take into consideration that there maybe database performance issues or network waits.

To add tolerance to Forms patience thay have added a great parameter called ‘networkRetries’ to the forms configuration file $ORACLE_HOME/forms/server/formsweb.cfg.  Set the value of the networkretries parameter to a suitable number according to your network characteristics needed. For example, networkRetries=30.  If the error continues to occur even after setting up an appropriate value for networkRetries, you should check firewall and proxies that may be blocking the applications server ports.

Conclusion and Resources:

We see that the classic way to start a Forms module still works. Nevertheless, the discontinuation of java plug-in support in recent browsers forced Oracle to react and to break new ground. Keep it up!

– Want to run Forms without an applet from HTML or mobile apps? This page is a good place to start.

– Want assistance from Oracle Forms industry experts? AuraPlayer has free consultation sessions available, click here to get in touch.

– Want to learn how to stay in control of your Oracle Forms environment and applications? Read our Essential Guide to troubleshooting errors on Oracle Forms – Download Now

To learn more about FSAL, click here.

Some interesting links about this topic are:


Known Causes of FRM-92101 Error In Forms [Note: 604633.1 on Metalink]


Subject: How To Fix The Forms Timeout Issue In Oracle Applications 11i


Understanding How network Retries Works [ID 332942.1]


Master note on Known Causes of FRM-92102 Error in Forms [ID 756369.1]


Understanding Oracle Forms timeout parameters (or should I say FORMS_TIMEOUT) FRM-92102 – A network error has occurred
Article Name
Understanding Oracle Forms timeout parameters (or should I say FORMS_TIMEOUT) FRM-92102 – A network error has occurred

Today I was at a client who was having trouble as their forms were disconnecting randomly after 15 minutes. They tried to play around with the TIMEOUT settings but they got bogged down in too many

Publisher Name
Publisher Logo

David Buch
Senior Products Manager

David, our Senior Products Manager, is a highly experienced professional specializing in product definition, innovations, and development, with broad customer understanding, and skillful people management. He has over 20 years of R&D work experience, and continues to excel in his expertise. When he is not working, David enjoys spending his time as a professional tuba player joining symphony orchestras and chamber ensembles.

Elizabeth Pearl
Relationship Manager

Before joining AuraPlayer, Elizabeth completed a Masters degree in Education and worked as a teacher. Elizabeth’s role as Customer Relationship Manager combines both her passion for technology and her deep desire to educate  others. On a daily basis, Elizabeth takes the valuable insights she gained as a teacher and uses them to rise within the world of tech. She uses her skills of active listening, organization, preparation, and clear communication to enhance the wonderful relationships she has with both coworkers and customers.


Elizabeth is originally from the United States but currently resides in England. In her spare time, she loves exercising, spending time with her family and friends, and playing volleyball.

Nathalie Wasserman
CFO & Operations Manager

Natalie is proud to be AuraPlayer’s Operations and Chief Financial Officer. She takes pride in her work, and loves being a part of the AuraPlayer family. Prior to working at AuraPlayer, Nathalie worked at various companies as an accountant. She attended the University College London (UCL), where she graduated with a Bachelor’s Degree in economics and business. She then went on to pursue a Master’s degree in Political Economies in Eastern Europe. 

Gwen Edwards
VP Business Development

An expert in helping businesses seize their potential and grow, Gwen is committed to take AuraPlayer to the next level. With over 30 years of experience in the high technology sector and working with Fortune 500 companies, she works as an advisor for growing businesses to help enhance their value and reach their business objectives. She’s a dynamic member of our team, leveraging her sales and marketing, and P&L experience to our current and future product suite.

Gwen also serves on a several private company boards in Silicon Valley, and is an active member of the angel investment network, Golden Seeds.

Yossi Nakash
CTO & Co-Founder

A true developer, Yossi has been developing and coding in Java / J2EE, C++, .Net, and C# for over 20 years, focusing mainly on the RD side of things. Entering the Oracle World about 10 years ago, Yossi immersed himself in the world of Oracle SOA, Weblogic, EBS and EBS Mobile, as well as the Java side of things.

Prior to joining Mia to found AuraPlayer, Yossi held the role of RD team leader at RadView and was a Java developer at Motorola.