The following sections describe known issues:
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:
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.
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>
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
In the standalone mode, there is no automatic port allocation for Oracle HTTP Server instances.
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.
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.
After a successful collocated OHS installation on the HPIA64 platform, the OHS startup metrics will fail to load if you restart the OHS instance through the Oracle Enterprise Manager Fusion Middleware Control console. You might get errors like: "Metrics are currently unavailable", or "Metrics are not configured."
Workaround:
To resolve this issue, logout and log in from Oracle Enterprise Manager Fusion Middleware Control console once the OHS starts.