Known Issues and Workaround

4 Known Issues and Workaround

This chapter describes the issues associated with Oracle HTTP Server.

In IBM AIX, OHS Server Startup Fails Even After Successful Installation and Configuration of Oracle HTTP Server

Issue

Impacted Platforms: IBM AIX

After successful installation and configuration of Oracle HTTP Server 12.2.1.4.0 , the Oracle HTTP Server (OHS) startup fails with following error:

exec(): 0509-036 Cannot load program httpd because of the following errors: 
rtld: 0712-001 Symbol CreateIoCompletionPort was referenced from module $ORACLE_HOME/wlserver/../lib/libclntsh.so(), but a runtime definition of the symbol was not found.

Workaround

Oracle HTTP Server 12.2.1.4.0 is bundled with IBM AIX Database client 12.1.0.2.0 version. The issue is related to the IOCP API symbols dependency in IBM AIX Database 12.1.0.2 client library. Enable the IOCP module in the machine where Oracle HTTP Server is installed to resolve this issue.

On IBM AIX in IBM POWER Systems (64-Bit), enable I/O completion ports (IOCP) before initiating the install process. To enable IOCP ports, set the status of the IOCP port to Available.

To check the IOCP status, run the following command:

$ lsdev | grep iocp

By default, IOCP status is set to Defined, and hence not enabled. The following example output shows that the IOCP status is set to Defined:

iocp0 Defined I/O Completion Ports

Complete the following steps to set IOCP status to Available:

Log in as root and run the following command:
```
smitty iocp
```
Select Change / Show Characteristics of I/O Completion Ports.
Change configured state at system restart from Defined to Available.
Run the lsdev command to confirm that the IOCP status is set to Available.
```
$ lsdev | grep iocp 
iocp0 Available I/O Completion Ports
```
Perform a system restart to make the changes permanent.

Parent topic: Known Issues and Workaround

In IBM AIX, Continuously Hitting a Web Application Through Oracle HTTP Server Generates a Large Error Log

Issue

Impacted Platforms: IBM AIX

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.

Workaround

This is a performance tuning issue that can be corrected by updating some of the IBM AIX system parameters and Oracle HTTP Server tuning parameters.

For example:

For IBM AIX system parameters:

Ensure that the following parameters are available in /etc/security/limits:
```
nofiles = -1
nofiles_hard = -1
```

Ensure that the following parameters are available in /etc/rc.net:

/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

Restart the computer.

For Oracle HTTP Server Configuration:

Set the mod_wl_ohs.conf file to 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>

Set the following in the httpd.conf file:

<IfModule mpm_worker_module>
          -
          -
          -
MinSpareThreads     200 [default value 25]
MaxSpareThreads     800 [default value 75]
          -
          -
          -
          -
</IfModule>

Parent topic: Known Issues and Workaround

Problem Setting an MPM Name in Fusion Middleware Control

Issue

Impacted Platforms: Generic

The operation of setting a Multi-Processing Module (MPM) name succeeds but a false misleading message stating that it has failed appears.

The following error message appears:

Error Setting performance Directives

Workaround

Retry the operation until it succeeds.

Parent topic: Known Issues and Workaround

Metrics Fail to Load After Restarting Oracle HTTP Server Through Oracle Enterprise Manager Fusion Middleware Control Console on HP IA

Issue

Impacted Platforms: Generic

After a successful collocated installation of the Oracle HTTP Server on the HP IA–64 platform, Oracle HTTP Server startup metrics fail to load if you restart the Oracle HTTP Server instance through Oracle Enterprise Manager Fusion Middleware Control Console. You might get one of the following errors:

Metrics are currently unavailable

Metrics are not configured

Workaround

Log out and log in from the Oracle Enterprise Manager Fusion Middleware Control Console after Oracle HTTP Server starts.

Parent topic: Known Issues and Workaround

mod_security SecRemoteRules Directive Use-case Does Not Work on HP-Itanium

Issue

Impacted Platforms: HP-Itanium

SecRemoteRules directive is configured to download mod_security rules from remote host. If the mod_security module is unable to download rules, no error message is logged in the ohs.log and mod_security log files.

Workaround

Remote server will have security rules in a text file as follows:

rultes.txt:

SecAction "id:'900006', phase:1, t:none, setvar:tx.max_num_args=255, nolog, pass"
SecRule REQUEST_URI "^/ohs" "id:1234,deny"

The mod_security.conf file will have one entry to load rules from remote server, as follows:

SecRemoteRules test https://remoteserver:4443/rultes.txt

Replace the line in the mod_security.conf file with the content of rultes.txt file.

Parent topic: Known Issues and Workaround

A Caution Message Appears at Startup for OHS and CLASSIC on AIX

Issue

Impacted Platforms: IBM AIX

When the installer is invoked for Oracle HTTP Server and CLASSIC on AIX operating systems, the following caution message is displayed:

bash-4.2$
/net/slcnas561/export/fa_porting01/ASCLASSIC_122131_shiphomes/stage-rc2/fmw_12
.2.1.4.0_fr_aix_ppc64.bin -J-Djava.io.tmpdir=/scratch/vsunkesu/tmp  
-invPtrLoc  /scratch/vsunkesu/122140/oraInst.loc
caution: excluded filename not matched:  sfx.ini
Launcher log file is
/scratch/vsunkesu/tmp/OraInstall2019-09-10_06-08-56AM/launcher2019-09-10_06-08
-56AM.log.
Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . Done

Workaround

The caution message is printed by the unzip tool and will not affect the installation.

Parent topic: Known Issues and Workaround

Launch of OHS and CLASSIC Installer Fails on AIX

Issue

Impacted Platforms: IBM AIX

Oracle HTTP Server and Classic installer fails to launch on AIX operating systems if "//" is present at the end of the value of the -J-Djava.io.tmpdir parameter.

For example:

-J-Djava.io.tmpdir=/scratch/xyz/tmp//

Workaround

Oracle recommends not to use // at the end of the value of -J-Djava.io.tmpdir.

For example:

-J-Djava.io.tmpdir=/scratch/xyz/tmp/

Parent topic: Known Issues and Workaround

An Incorrect Step Appears on the Installation Complete Screen

Issue

Impacted Platforms: Generic

When you complete a standalone Oracle HTTP Server installation, the step Start Node Manager and Domain Servers is displayed as one of the next steps you should take after installation.

Workaround

This information is incorrect because there are no domain servers configured during the standalone installation.

Parent topic: Known Issues and Workaround

Warning Messages in make.log File

Issue

Impacted Platforms: IBM AIX

While installing Oracle Web Tier 12c on AIX operating systems, warning messages may appear in the ORACLE_HOME/install/make.log file.

Workaround

These messages can be safely ignored.

Parent topic: Known Issues and Workaround