There have been known issues where if you plan to run Oracle Forms using OHS with SSL/TLS (using the HTTPS protocol) and the OHS HTTP port (8888 by default) is disabled in httpd.conf, connections to the Forms application drop after a small period of time. The error which end users receive is:
FRM-92103: A network error or server failure has occurred. You will need to restart your application.
Look in the ohs1.log located in %ORACLE_INSTANCE%\diagnostics\logs\OHS\ohs1. If you see the following errors inside the log file:
[timestamp] [OHS] [ERROR:32] [OHS-2079] [core.c] [host_id: hostname] [host_addr: ip_address] [pid: ###] [tid: ###] [user: USER] [VirtualHost: hostname.domain:8890] nzos handshake error, nzos_Handshake returned 29039(server hostname.domain:8890, client ::1)
[timestamp] [OHS] [ERROR:32] [OHS-2171] [core.c] [host_id: hostname] [host_addr: ip_address] [pid: ###] [tid: ###] [user: USER] [VirtualHost: hostname.domain:8890] NZ Library Error: SSL negotiation error [Hint: too restrictive SSLCipherSuite]
OHS may need to be enabled at least at the loopback address level. If your organization has requirements where the OHS HTTP port has to be disabled for incoming and outgoing connections, configuring it to run only at the loopback level will still satisfy this requirement. To configure this, you will need to follow these steps:
1. Go to %ORACLE_INSTANCE%\config\OHS\ohs1 ($ORACLE_INSTANCE/config/OHS/ohs1 in Unix) and open up httpd.conf in a text editor (make a backup first).
2. Look for the commented “#Listen 8888” parameter. Uncomment the parameter and specify the loopback address:
3. Save and close the file.
4. Restart OHS either from OPMN or Enterprise Manager.
After applying the steps above, the FRM-92103 errors should disappear when running Forms with the OHS HTTPS port.
Source: Oracle Support note 1471204.1