This chapter describes unresolved issues known to exist in Oracle HTTP Server 12c (12.2.1).
The following sections describe known issues:
Section 1.2, "Upgrading from Earlier Releases of Oracle HTTP Server"
Section 1.3, "Known Issues in Oracle HTTP Server 12c (12.2.1)"
Chapter 2, "Issues Resolved", describes known issues in 12c (12.1.x) that have been resolved in Oracle HTTP Server 12c (12.2.1).
This issue applies to WLS plug-ins for Apache 2.2 on Windows only (not applicable for OHS or any other Listeners/Web Servers).
If an IPv6 address is specified for WebLogicHost/WebLogicCluster parameter, then WLS plug-in may be unable to resolve this IPv6 address. This is due to a bug in the APR library that is shipped Apache httpd 2.2.x (underlying APR library, libapr-1.dll), and is resolved in Apache httpd 2.2.24.
To upgrade your Fusion Middleware environment (and OHS) to 12.2.1 from an earlier release, follow the instructions in Upgrading with the Upgrade Assistant. If you are upgrading a collocated Oracle HTTP Server setup (not a standalone installation), then you must perform some manual steps after you complete the Upgrade Assistant. For detailed information about these steps, see "Upgrading from Earlier Releases of Oracle HTTP Server" in Administering Oracle HTTP Server.
This section contains descriptions of unresolved issues known to exist in Oracle HTTP Server 12c (12.2.1). The following sections describe these issues:
Section 1.3.2, "Server Configuration Page for OHS Fusion Middleware Control"
Section 1.3.3, "FIPS Mode Support for OTD 12.2.1 on AIX.PPC64"
Section 1.3.5, "DMS Displays Incorrect Message if OHS is Down"
Section 1.3.6, "No Automatic Port Allocation for Standalone Instances"
Section 1.3.7, "Oracle HTTP Server in Fusion Middleware Control Does Not Recognize Deployer Role"
Section 1.3.8, "Problem Setting MPM Name in Fusion Middleware Control"
Bug 21778276
When SSLVerifyClient is configured in the directory context, it forces an SSL renegotiation with the reconfigured client verification level after the request was read, but before the response is sent. GCM ciphers
(TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256) are found not to be working during the SSL renegotiation.
To work around this issue, disable GCM ciphers by removing GCM ciphers from the SSLCipherSuite directive in ssl.conf. This is required only when you have a SSLVerifyClient directive configured in the directory context.
Bug 21816029
In the online Help text for this page, the following content applies:
In the console, the updated value of attributes is displayed even when the changes made in edit Session have not been activated.
This is not the case with the list of enabled modules displayed on the Server Configuration Page. It displays only those modules which are present under <DOMAIN_HOME>/config/fmwconfig/components/OHS/<instanceName>/moduleconf and does not include the modules that were enabled or disabled in the current session that is not yet activated.
Bug 21845371
When FIPS mode is enabled in an OTD Instance on AIX, OTD instance startup fails with the following error:
nzos_SetFipsMode is returning NZ error 29231 which is NZERROR_TK_CE_INIT = 29231 /* Crypto engine failed to initialize */
The OTD server does not start because of FIPS initialization failure due to RSA third party issues.
The solution to this issue is to take the following actions:
Create short symlinks from a short write-protected directory to library folders inside ${MW_HOME} as shown in this example:
ln -s /usr/otd_user/12cOTD/mw_home/otd/lib /usr/lib1 ln -s /usr/otd_user/12cOTD/mw_home/oracle_common/lib /usr/lib2 ln -s /usr/otd_user/12cOTD/mw_home/lib/ /usr/lib3
Where: MW_HOME is - /usr/otd_user/12cOTD/mw_home and /usr is the shortest secure folder
In this example in which the OTD instance is named "test", edit the script in
${DOMAIN_HOME}/config/fmwconfig/components/OTD/instances/otd_test_Machine-0/bin/startserv
Change SERVER_LIB_PATH from
SERVER_LIB_PATH="${SERVER_LIB_DIR}:${ORACLE_HOME}/lib:${ORACLE_HOME}/oracle_common/lib"
to
SERVER_LIB_PATH=/usr/lib1:/usr/lib2:/usr/lib3
18410116 brought forward to 12.2.1 re:gopi.challa
IBM-AIX users continuously hitting a web application that has many users (for example, greater 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.
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 reboot 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 *.jsp
WebLogicCluster <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>
16779920
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
16278756
In the standalone mode, there is no automatic port allocation for Oracle HTTP Server instances.
18092446
Oracle WebLogic Server supports these default roles: Admin, Deployer, Operator, and Monitor. In previous release, the Deployer role was supported in the JMX Framework and Fusion Middleware Control.
The user of the Deployer role will be able to log in to Fusion Middleware Control. For the particular page or integrator area, whether or not the Deployer role should be enabled, depends on the page's functionality and Deployer role privileges. It is up to the page or integrator owner (such as Oracle HTTP Server, IDM, and so on) to decide. Oracle HTTP Server does not support the Deployer role since this role does not make sense for the proxy tier such as Oracle Traffic Director or Oracle HTTP Server.
21550357
There is an intermittent problem in setting the MPM Name value of the Performance Directives page of Fusion Middleware Control.
An error message appears and displays the text:
Error Setting performance Directives
Workaround:
If you encounter this error, retry the operation until it succeeds.