The Application Server running Forms show numerous errors similar to the following:
On Windows , in the event viewer:
Faulting application frmweb.exe, version 10.1.2.2, faulting module
kernel32.dll, version 5.2.3790.2756, fault address 0x00015e02.
On Linux, in /var/log/messages :
kernel: frmweb: segfault at 000000006974655e rip 00000000081d3ca9 rsp 00000000ffff9d2c error 4
(most numbers are not significant, they will likely differ on your system)
On Unix, huge core files can also be generated, possibly causing a system hang or various problems.
The users are closing the Forms sessions using the browser and not by using the exit mechanisms in the Forms.
To prevent these error messages, close the Forms application normally before closing the browser.
If using Internet Explorer, you can pop-up a message window when users attempt to close the browser by following indications from NOTE 605327.1 – How To Trap Attempts At Closing The Parent Browser Running A Forms Application
On Unix, setting “ulimit -c” to “0”, for example for Forms will prevent writing of further “core” files. This can avoid completely the risk of a huge frmweb “core” file possibly impacting the system in case a user would close his browser without exiting Forms first:
In forms 10g this could be done prior to starting OC4J_BI_Forms with opmnctl:
ulimit -c 0
In forms 11g this could be set in the dedicated WLS_FORMS server section of the file DOMAIN_HOME/bin/setDomainEnv.sh:
if [ “$(SERVER_NAME)” = “WLS_FORMS” ] ; then
ulimit -c 0