Topics
Known issues in 12c (12.1.2) that have been resolved in Oracle HTTP Server 12c (12.1.3) are described in Bugs Fixed in this Release.
This section contains descriptions of unresolved issues known to exist in Oracle HTTP Server 12c (12.1.3).
Topics
Continuously Hitting Web Application Through OHS on IBM-AIX Might Generate a Large Error Log
Starting Node Manager in Collocated Environment Generates System Messages
Oracle HTTP Server in FMW Control Does Not Recognize Deployer Role
Oracle HTTP Server Configuration Assistant Launcher Fails on Solaris 5.10
Default Value for the MaxPostSize Web Server Plug-in Parameter has Changed
Installing Oracle HTTP Server on Oracle Linux 7 Environments
Issue
Impacted Platforms: Generic
The startComponent.sh
and stopComponent.sh
scripts fail when executed from a directory without write permission.
Workaround
To avoid this situation, execute startComponent.sh
or stopComponent.sh
from $DOMAIN_HOME/bin/
or any other directory with write permission.
Issue
Impacted Platforms: Generic
While launching Oracle HTTP Server instance, this message appears:
Couldn't set permissions on unix domain socket
in Oracle HTTP Server Instance log while loading the cgid module (mod_cgid). This message indicates that the mod_cgid is not loaded because the cgisock
log file path length exceeds the actual character array length of sun_path
variable defined in /usr/include/sys/un.h
.
Workaround
To work around this issue, edit the httpd.conf
file for the instance and set the Scriptsock value to /var/tmp/cgisock
instead of ${ORACLE_HOME}/network/log/cgisock
. You can find the httpd.conf
file in $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/$INSTANCE_NAME/httpd.conf
Issue
Impacted Platforms: Generic
IBM-AIX users continuously hitting a web application that has many users (for example, more than 400) through Oracle HTTP Server might experience a large error log being generated. This is most likely a tuning issue that can be corrected by updating certain IBM-AIX system parameters and Oracle HTTP Server tuning parameters, as described as shown in the following examples.
Workaround
This is most likely a tuning issue that can be corrected by updating certain IBM-AIX system parameters and Oracle HTTP Server tuning parameters, as described as shown in the following examples.
For AIX system parameters:
In /etc/security/limits
, should have the following parameters:
nofiles = -1 nofiles_hard = -1
In /etc/rc.net
, should have the following parameters:
/usr/sbin/no -o sb_max=6192000 /usr/sbin/no -o tcp_sendspace=4096000 /usr/sbin/no -o tcp_recvspace=4096000 /usr/sbin/no -o udp_sendspace=65536 /usr/sbin/no -o udp_recvspace=655360 /usr/sbin/no -o rfc1323=1 /usr/sbin/no -o ipqmaxlen=150 /usr/sbin/no -o clean_partial_conns=true
You will need to restart your machine.
For Oracle HTTP Server Configuration:
In mod_wl_ohs.conf
, should look like the following: example:
LoadModule weblogic_module "${PRODUCT_HOME}/modules/mod_wl_ohs.so" # This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level <IfModule weblogic_module># WebLogicHost <WEBLOGIC_HOST># WebLogicPort <WEBLOGIC_PORT># MatchExpression *.jspWebLogicCluster <host-name>:<port>,<host-name>:<port>,<host-name>:<port>ConnectTimeoutSecs 99999 //[Optional parameter]WLIOTimeoutSecs 99999 //[default value 300]WLSocketTimeoutSecs 99999 //[default value 2]MatchExpression *<Location /diagservlet># SetHandler weblogic-handler WLSRequest On WebLogicCluster<host-name>:<port>,<host-name>:<port>,<host-name>:<port># PathTrim /weblogic# ErrorPage http:/WEBLOGIC_HOME:WEBLOGIC_PORT/ </Location></IfModule>
In httpd.conf
, set the following:
<IfModule mpm_worker_module> - - - MinSpareThreads 200 [default value 25] MaxSpareThreads 800 [default value 75] - - - - </IfModule>
Issue
Impacted Platforms: Generic
If you are using Fusion Middleware Control or WLST commands to configure SSL for Oracle HTTP Server, you cannot configure the TLSv1.1(nzos_Version_1_1) and TLSv1.2(nzos_Version_1_2) protocols for the SSLProtocol directive or for these SSLCipherSuite directive ciphers:
SSL_RSA_WITH_RC4_128_SHA
SSL_RSA_WITH_RC4_128_MD5
SSL_RSA_WITH_AES_128_CBC_SHA
RSA_WITH_AES_128_CBC_SHA256
RSA_WITH_AES_256_CBC_SHA256
RSA_WITH_AES_128_GCM_SHA256
RSA_WITH_AES_256_GCM_SHA384
ECDHE_ECDSA_WITH_AES_128_CBC_SHA
ECDHE_ECDSA_WITH_AES_256_CBC_SHA
ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
ECDHE_RSA_WITH_AES_128_CBC_SHA
ECDHE_RSA_WITH_RC4_128_SHA
ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
If SSL is enabled for Oracle HTTP Server Virtual Hosts or the SSL configuration has been modified from the SSL Configuration page of Fusion Middleware Control configuration screen or WLST commands, the configuration of the above listed protocols and ciphers in ssl.conf
will be lost.To make any changes related to the SSL configuration for these protocols and ciphers, edit ssl.conf
directly by using the Advanced Configuration page in Fusion Middleware Control.
Workaround
No workaround available
Issue
Impacted Platforms: Generic
In a collocated environment, when connecting to Node Manager by using the startNodeManger
command (for example, when using the startComponent command as in Starting Oracle HTTP Server Instances from the Command Line), you might encounter many system messages upon startup. You can ignore these messages.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
In previous releases, a user granted the WLS deployer role was not able to log in to Oracle Fusion Middleware Control. As of Oracle Fusion Middleware Control 12c (12.1.3), the deployer role is supported in JMX Framework and WLS FMW Control EXCEPT Oracle HTTP Server 12.1.3, where FMW Control does not recognize this role. Users granted deployer role will not be able to access Security, Administration or Control functionality.
Workaround
No workaround available
Issue
Impacted Platforms: Generic
The Oracle HTTP Server ServerName directive cannot support IPv6 actual addresses as it does not accept IPv6 addressing format.
Workaround
If you must use IPv6, then create a domain name for the specific IPv6 address and use that in ServerName directive.
Issue
Impacted Platforms: Generic
A bad CLASSPATH
environment variable can block the WebLogic Scripting Tool (WLST) from starting. If a bad CLASSPATH
is set in your environment variables and you attempt to start WLST, you might see a message like:
Problem invoking WLST - java.lang.NoClassDefFoundError:javax/enterprise/deploy/spi/exceptions/DeploymentManagerCreationException
Workaround
If you encounter a similar error, check your environment variables to see if CLASSPATH
is correctly specified.
Issue
Impacted Platforms: Generic
While creating an Oracle HTTP Server domain, ORACLE_HOME/ohs/common/bin/config.sh
launcher fails and throws this error:
bash-3.2$ ./config.sh Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':1.0' as the value of the DISPLAY variable. at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65) at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110) at java.security.AccessController.doPrivileged(Native Method) at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:188)
Workaround
If you encounter this problem, apply the respective patch for your platform. These are available from Oracle Support:
For Solaris.X64, obtain patch 17458572
For Solaris.SPARC64, obtain patch 17458571
Issue
Impacted Platforms: Generic
In several places, the Administering Oracle HTTP Server12c documentation discusses the SSL version 3 (SSLv3) security protocol. Because of security concerns, Oracle strongly recommends that you disable the SSLv3 security protocol from Oracle HTTP Server.
To disable SSL security protocols from Oracle HTTP Server:
Locate the ssl.conf
file in the staging directory and the runtime directory.
You can find the ssl.conf
files in the following locations:
Staging directory: DOMAIN_HOME
/config/fmwconfig/components/OHS/
componentName
Runtime directory: DOMAIN_HOME
/config/fmwconfig/components/OHS/instances/
componentName
Edit the security declaration to use a non-SSL protocol.
For example, to remove the SSLv3 security protocol:
SSLProtocol -SSLv3
or to add the TLS version 1.0 and 1.2 security protocols:
SSLProtocol nzos_Version_1_1 nzos_Version_1_2
or to add the TLS version 1.0, 1.1, and 1.2 security protocols:
SSLProtocol nzos_Version_1_0 nzos_Version_1_1 nzos_Version_1_2
Save the files and restart Oracle HTTP Server.
Note:
If you are editing files manually, ensure you edit a currently configured value instead of adding another. It could be easy to add a global parameter when it will be overridden by a value in the VirtualHost.
Using the new nzos_Version_*
syntax is now preferred. If you are using Oracle Fusion Middleware Control, this is how security will be configured.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
The documentation for the MaxPostSize web server plug-in parameter in Oracle Fusion Middleware Using Oracle WebLogic Server Proxy Plug-Ins 12.1.2 and Oracle Fusion Middleware Administering Oracle HTTP Server describes its default value as -1. In this release, the default value has been changed to 0.
Workaround
No workaround available.
Issue
Impacted Platforms: Windows
FIPS is available only on the UNIX/Linux platform. It is not available on the Windows platform. See OHS Release 12c (12.1.2) Supports FIPS 140, SSL FIPS Mode Can Be Configured as a SSLFIPS Directive, and SSLFIPS in Administering Oracle HTTP Server.
Workaround
No workaround available.
Issue
Impacted Platforms: Oracle Linux
Oracle HTTP Server 12c (12.1.3) can be installed into Oracle Linux 7 (OEL7) environments only if you run the Oracle Universal Installer (OUI) from the command line with the -ignoreSysPrereqs
option, for example:
./runInstaller -ignoreSysPrereqs ...
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
When SSL certificate DN is queried using the CGI interface, the order of attributes of the DN is changed from:
Country, location, Organisation, Organisational Unit, Common Name, Email.
to:
Email, Common Name, Organisational Unit, Organisation, Location, Country.
Workaround
No workaround available.
This section contains descriptions of unresolved issues known to exist in Oracle HTTP Server 12c (12.1.2).
Topics
Using shutdown() Without Parameters Shuts Down WebLogic Server
nmStart(), nmServerStatus(), and nmKill() Require ServerType Parameter
Create DOMAIN_HOME/servers/<instancename>/logs manually when Diagnosing Start-up Failures
Installer Sporadically Hangs on Specify Security Updates Screen
Warning Appears if No Oracle HTTP Server Instance is Created
Backslashes in Paths in ohs.plugins.nodemanager.properties must be Escaped
Set PATH Environment Variable Manually if OHS on Windows Fails to Start
Recovering Instance on Managed Node Requires tar/untar Commands
OHS Instance Creation with Config Wizard Does Not Require Machine Assignment
Create Log Directory Manually When Diagnosing Startup Failures
OHS on UNIX Might Not Start When Listening Port is Configured in Reserved Range
Issue
Impacted Platforms: Generic
The WebLogic Scripting Tool (WLST) command shutdown(<instancename>) is used to stop an Oracle HTTP Server instance in a WebLogic domain. Be aware that using shutdown() with no parameters will shut down the administration server and exit WLST.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
Multiple WLST scripts are provided within an Oracle home. Use the WLST script in ORACLE_HOME/ohs/common/bin, which provides access to Oracle HTTP Server commands and other Fusion Middleware commands.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
This version of Oracle HTTP Server has no command to list all Oracle HTTP Server instances, states and ports. This is different than Oracle HTTP Server 11g, where such information was available by using the command opmnctl status
.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
When using the Configuration Wizard to create or update a standalone domain, the Configuration Wizard does not present a Configuration Summary Screen. The user does not have the option to go back and make changes.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
All standalone Oracle HTTP Server instances created by using the Configuration Wizard start in state UNKNOWN
.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
In the standalone mode, using the WLST command nmServerStatus()
returns UNKNOWN
for non-existent instances (for example, if you have a typo in the serverName=
argument). Effectively it cannot distinguish between non-existent instances and instances that really are in UNKNOWN
; that is, just after creation, as (see Standalone Instances Start in UNKNOWN State).
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
In the standalone mode, there is no automatic port allocation for Oracle HTTP Server instances.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
The offline WLST commands nmStart(), nmServerStatus(), and nmKill(), required for management of standalone Oracle HTTP Server instances, all require the serverType='OHS'
parameter when managing Oracle HTTP Server. If the serverType parameter is omitted, the command defaults to 'AdminServer" and error messages might be misleading when managing Oracle HTTP Server instances.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
Currently standalone domain update enables you to delete instances in a RUNNING
state. This should not be done as it is harmful to Oracle HTTP Server. All OHS instances should be SHUTDOWN
(or UNKNOWN
) before deletion.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
The keystores.xml file contains private keys that should not be on a demilitarized zone (DMZ; that is, the zone between the internal and external firewalls) machine.
Workaround
If you unpack a domain on a machine in the DMZ, you must remove keystores.xml from it. To do so, go to $domain/config/fmwconfig/ and, from the command line, use this command:
rm $domain/config/fmwconfig/keystores.xml
Issue
Impacted Platforms: Windows
On the Windows platform, Oracle HTTP Server requires Microsoft Visual C++ run-time libraries to be installed on the system in order to function. If they are not installed, Oracle HTTP Server might exit with no output or generate an error dialog box, depending on registry settings.
Workaround
If Oracle HTTP Server fails to start and no error messages are logged by Oracle HTTP Server in the server error log or in Node Manager logs, follow this procedure to diagnose the problem:
Verify that the following run-time library is installed:
Visual C++ Redistributable for Visual Studio 2012 (x64), at
https://www.microsoft.com/en-in/download/details.aspx?id=30679
Note:
After installing this package, install any service packs or other fixes to this package which are recommended by Microsoft.
If this package was not installed previously, try to start Oracle HTTP Server again after installing it.
Attempt to start Oracle HTTP Server from a command prompt.
Create the DOMAIN_HOME/servers/<ohs-instancename>/logs directory if it has not yet been created by Oracle HTTP Server.
Try to start Oracle HTTP Server using Fusion Middleware Control or WLST.
Copy the file DOMAIN_HOME/servers/<ohs-instancename>/logs/lastinvocation.log to a new file startohs.cmd.
Open a new command prompt and run startohs.cmd in that new command prompt.
If it generates error messages after the script runs, use those messages to diagnose the startup failure.
If it does not generate error messages after the script runs, proceed to the next step.
Note:
Oracle HTTP Server does not function properly when started from a command prompt in this manner. This mechanism for starting Oracle HTTP Server is for diagnostic purposes only.
Collect Windows error information when attempting to start Oracle HTTP Server
Error reporting for Oracle HTTP Server library errors might be inhibited on your system. Refer to the following Microsoft article for information on verifying or correcting error reporting:
"HOWTO: How To Change Hard Error Popup Handling in Windows NT", at
http://support.microsoft.com/kb/128642
If ErrorMode is set to 1, library errors might not be reported for Oracle HTTP Server. Change the mode to 0 to enable hard error pop-ups or change the mode to 2 to enable reporting to the Windows event log.
Note:
If this is changed to 0, set it back to the previous value immediately after collecting diagnostic information as it can result in operational problems if errors occur when the server is unattended.
The recommended setting is 2.
Change ErrorMode to the desired value.
Try to start Oracle HTTP Server using Fusion Middleware Control or WLST or the startohs.cmd script which was created in the previous step.
Check for diagnostic information in a hard error popup or in the Windows event log, depending on the setting of ErrorMode.
To check the Windows event log, open Windows Event Viewer and view the logs for Event Viewer (Local) / Windows Logs / Application
Find the event log entries written at the time of the attempt to start Oracle HTTP Server.
Errors locating run-time libraries might be reported as SideBySide errors with event ids 33 or 35, which text describing the Oracle library attempting to load the library and the specific library being loaded. Example:
level=Error Source=SideBySide Event Id = 33 Activation context generation failed for "C:\work\Oracle\MD1212\ORACLE~1\bin\oraiau.dll". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="amd64", publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.
The indicated library must be installed. This example shows VC90, which is the Visual C++ Redistributable for Visual Studio 2012 (x64) library described in step 1 above.
Restore ErrorMode to the previous setting.
Issue
Impacted Platforms: Generic
If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory DOMAIN_HOME/servers/<instancename>/logs if it does not exist, then attempt to start the instance again so that all diagnostic information can be written. The log file lastinvocation.log, used for diagnosing some types of startup failures, will not be written if this log directory does not exist.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
Occasionally, the Oracle WebLogic Server or Oracle HTTP Server installation process hangs on the Specify Security Updates screen (5 of 9) in the NextGen Oracle Universal Installer (OUI). When this occurs, all of the buttons at the bottom of the OUI screen are disabled and inaccessible and the links to go back in the left-hand pane are similarly inactive.
Workaround
When this situation occurs, you must forcibly exit the installer by pressing CTRL-C in the xterm where you initially launched the installer. You can then restart and walk through the installation normally.
Issue
Impacted Platforms: Generic
In a WebLogic Server domain, while you are not required to create any Oracle HTTP Server instances, if you do not, you will receive a warning is displayed. You can ignore this warning.
Workaround
No workaround available.
Issue
Impacted Platforms: Windows
Any paths placed in Windows implementations of ohs.plugins.nodemanager.properties that include backslashes must have those backslashes escaped.
Workaround
You must do this manually after upgrading from Oracle HTTP Server 11g where paths with backslashes were migrated from opmn.xml to ohs.plugins.nodemanager.properties.
For example:
environment.TMP = C:\Users\user\AppData\Local\Temp\1
Must be modified manually to:
environment.TMP = C:\\Users\\user\\AppData\\Local\\Temp\\1
Issue
Impacted Platforms: Generic
If you try to create an instance with the name "adminserver", Oracle HTTP Server throws an exception post after which you will not be able to create instances, even if they have valid names. Therefore, do not attempt to create instances that use the same name as a given administration server.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
If you attempt to obtain metrics when Oracle HTTP Server is not running, DMS will display an incorrect message on displayMetricTables.display:
MetricTables(servers='ohs1',servertype='OHS') Traceback (innermost last): File "<console>", line 1, in ? File "/scratch/oracle/Middleware/oracle_common/common/wlst/OracleDMS.py", line 67, in displayMetricTables File "/scratch/oracle/Middleware/oracle_common/common/script_handlers/oracle dms_handler.py", line 1105, in oracledmsDisplayMetricTables File "/scratch/oracle/Middleware/oracle_common/common/script_handlers/oracle dms_handler.py", line 648, in oracledmsHandleException NameError: ora_mbs
Workaround
No workaround available.
Issue
Impacted Platforms: AIX
When running Oracle HTTP Server on AIX, if ULIMIT values of file handlers are small, Node Manager console/log throws "java.io.IOException: error=24, Too many open files" error on AIX.
Workaround
To resolve the issue, increase the ULIMIT values of file handlers as described here:
Log in as the root user.
Open /etc/security/limits file.
Edit the file and set the following values:
nofiles=8192
nofiles_hard=65536
Reboot the machine to enable the changes.
Issue
Impacted Platforms: Windows
If Oracle HTTP Server fails to start on Windows and no log files are generated, the PATH environment variable must be manually specified.
Workaround
To do so, edit the Oracle HTTP Server nodemanager.properties file for this component (found in the domain directory) by doing the following:
Edit config\fmwconfig\components\OHS\ohs1\ohs.plugins.nodemanager.properties.
Add the following two lines:
environment.ORACLE_HOME = MW_HOME environment.PATH =%ORACLE_HOME%\\ohs\\bin;%ORACLE_HOME%\\bin;C:\\Windows;C:\\Windows\\system32
Where MW_HOME is the path to the middle ware install, for example:
environment.ORACLE_HOME = C:\\Oracle\\Middleware\\Oracle_Home
Note that all backslash file separators must be escaped with a backslash.
Save the file.
For Web Logic Server domains, replicate the changes in the run-time area.
For more information on the nodemanager.properties file, see ohs.plugins.nodemanager.properties in Administering Oracle HTTP Server.
Start Oracle HTTP Server as described in Starting Oracle HTTP Server Instances in Administering Oracle HTTP Server.
Issue
Impacted Platforms: Generic
Use tar
/untar
commands for recovering an instance on an managed node rather than pack
/unpack
. Pack
/unpack
are used for recovery on an administration node. pack/unpack are applicable to just the administration node; managed nodes must use tar/untar.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
When creating an Oracle HTTP Server instance by using the Configuration Wizard, you do not need to assign it to a machine. This is different behavior than you would experience when creating an instance by using the FMW Control's Create OHS command (described in Creating an Instance by Using Fusion Middleware Control in ), where you are prompted for a machine name.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
On some occasions, httpd.exe will fail to start, displaying the following error:
Error: The Side-by-Side configuration information for "ORACLE_HOME\bin\ORAIAU.DLL" contains errors.
This happens if you are missing the SP1 version of the 64-bit redistributable. You can obtain this file at:
http://www.microsoft.com/en-us/download/details.aspx?id=2092
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
When updating the SSL wallet in Fusion Middleware Control, the SSLWallet directive in ssl.conf might be saved incorrectly.
Oracle HTTP Server expects something similar to this form:
SSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${ COMPONENT_NAME}/keystores/wallet2"
The incorrect directive might look like this:
SSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores//OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/ohs1/keystores/wallet2"
This incorrect directive will prevent Oracle HTTP Server from starting successfully and a message similar to the following might appear in the OHS error log if OHS startup fails:
server www.example.com:443 has an invalid wallet: file:/OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/instances/ohs1/keystores//OHS/user_projects/domains/base_domain/config/fmwconfig/components/OHS/ohs1/keystores/wallet2 :: 28759
Workaround
To resolve the issue, use the Advanced Configuration feature in FMW Control to select the file ssl.conf and edit it to correct the SSLWallet directive.
Issue
Impacted Platforms: Generic
The apxs program provided with Oracle HTTP Server supports the -a and -A options for editing the configuration in a standalone domain to include the new module. This feature requires that the CONFIG_FILE_PATH environment variable point to the instance configuration directory.
If CONFIG_FILE_PATH is not set before invoking apxs, the error message might provide incorrect information for setting CONFIG_PATH. For the proper setting of CONFIG_FILE_PATH, see Configuring the Oracle HTTP Server Environment to Use the apxs Script in Administering Oracle HTTP Server.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory DOMAIN_HOME/servers/<instancename>/logs if it does not exist, then attempt to start the instance again so that all diagnostic information can be written. The log file lastinvocation.log, used for diagnosing some types of startup failures, will not be written if this log directory does not exist.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
createOHSTestDomain()
is intended only for WLST offline mode. If WLST is currently connected to an administration server, use the WLST command disconnect()
to disconnect before using createOHSTestDomain()
. If createOHSTestDomain()
is used in online mode, the resulting error messages will not describe the usage problem.
Workaround
No workaround available.
Issue
Impacted Platforms: UNIX
In some UNIX environments that access their root file system using a link, Oracle HTTP Server might not start even if it is properly configured to listen on a port in the reserved range. This occurs when the /etc/cap.ora
file is not located on a locally mounted block device.
Workaround
If you are encountering this problem, contact Release Management and download and apply the Release 12.1.2 backport patch.
Issue
Impacted Platforms: Generic
FIPS is available only on the UNIX/Linux platform. It is not available on the Windows platform. See OHS Release 12c (12.1.2) Supports FIPS 140, SSL FIPS Mode Can Be Configured as a SSLFIPS Directive, and SSLFIPS in .
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
When SSL certificate DN is queried using the CGI interface, the order of attributes of the DN is changed from:
Country, location, Organisation, Organisational Unit, Common Name, Email.
to:
Email, Common Name, Organisational Unit, Organisation, Location, Country.
Workaround
No workaround available.