There have been reports in many Forms installations where the Forms application hangs when an ALERT (SHOW_ALERT for example) is supposed to appear. A patch, 12433970, is available to fix this problem (see https://pitss.com/us/2012/07/10/oracle-forms-alert-freeze/ for more information). However, there are cases where Oracle Forms freezes when an alert is supposed to appear even if the patch is applied. Also, in Forms versions 11.1.1.6 and 11.1.2.1, this patch is included in these patchsets.
This has resulted in the 12433970 patch not fixing the problem. Another fix exists which has been known to fix the problem. This only requires a few changes in a couple of configuration files, and the environment does NOT need to be shut down. To apply this fix, you will need to do the following:
- Go to %ORACLE_INSTANCE%\config\FormsComponent\forms\server
- Make a backup of webutiljpi.htm
- Open up webutiljpi.htm in a text editor
- Look for all of the PARAM tags after <SCRIPT LANGUAGE=”JavaScript” … tag. Before the PARAM NAME=”ARCHIVE” tag, add the following line into the document:
- <PARAM NAME=”cache_archive_ex” VALUE=”%cache_archive_ex%”>
- Save and close the file.
- Go to %DOMAIN_HOME%\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_11.1.#\config
- Make a backup of formsweb.cfg
- Open up formsweb.cfg in a text editor
- Add the following parameter to each configuration section in formsweb.cfg such as default, webutil, or any application-related sections:
- cache_archive_ex=jacob.jar;preload
- Example if you have a custom jar file containing your icons and you are using WebUtil:
- cache_archive_ex=jacob.jar;preload,pitss.jar;preload
- NOTE: As you can see above, while each jar file is still separated by a comma, the “;preload” must be added at the end of the jar file before the comma. These jar files excluding the ones which start with “frm” should only be deployed here.
- If you have any jar files excluding the jar files which start with “frm” in the archive parameter, please remove them from the parameter.
- Repeat for all other sections in formsweb.cfg that you are using.
- Remove jacob.jar from all WebUtilArchive parameters in the file. Each WebUtilArchive should now look like this:
- WebUtilArchive=frmwebutil.jar
- Save and close the file.
After applying the changes above, start a new browser session (close all open browser windows first). You will notice that the application no longer hangs when an alert or dialog box appears. NOTE: If you notice that the problem is still occurring, try clearing your browser cache as well as your Java cache.
Source: Oracle Support note 1328039.1
