7 Oracle HTTP Server

This chapter describes issues associated with Oracle HTTP Server. It includes the following topics:

Section 7.1, "General Issues and Workarounds"
Section 7.2, "Configuration Issues and Workarounds"

7.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topics:

Section 7.1.1, "Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle Internet Directory 10g Release (10.1.2)"
Section 7.1.2, "Log Error Message"

7.1.1 Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle Internet Directory 10g Release (10.1.2)

Oracle does not support using the version of Oracle HTTP Server that is supplied with Oracle9iAS Release 1 (1.0.2.2.x) as a front end to OC4J supplied with Oracle Application Server 10gRelease 2 (10.1.2). You must not use mod_proxy to route data between these two components.

Always use mod_oc4j to route data to and from OC4J supplied with Oracle Application Server 10g (10.1.2). Use mod_proxy to route data between Oracle HTTP Server component supplied with Oracle9iAS Release 1 (1.0.2.2.x) and OC4J supplied with Oracle9iAS Release 1 (1.0.2.2.x).

7.1.2 Log Error Message

During operations where mod_oc4j calls mod_osso (such as login and logout), the following error message is printed to the Oracle HTTP server log:

[Mon Jun 27 23:57:07 2005] [error] [client 139.185.173.23] [ecid:
90258476571,1] MOD_OC4J_0376: Request initial processing failed in ac worker with
HTTP status code 1. This status will be passed back to the listener for error
handling.

This error message is harmless and can be ignored. It will be removed in a future release.

7.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

Section 7.2.1, "FastCGI Sockets Path Length Error"
Section 7.2.2, "Oracle HTTP Server Does Not Start After Enabling Port Tunneling or SSL in mod_oc4j"
Section 7.2.3, "Redirects Break If OracleAS Web Cache is Turned Off or is Disabled"

7.2.1 FastCGI Sockets Path Length Error

On most platforms, the path for sockets used by FastCGI is limited to 108 characters. If an error such as the following is encountered, use the FastCgiIpcDir directive to specify a path name that is significantly shorter than 108 characters, such as /tmp:

Thu Oct 16 12:55:06 2003] [error] [client 148.87.9.44] [ecid: 82608810576,1]
FastCGI: failed to connect to (dynamic) server
"/opt/oracle/inst/Apache/Apache/fcgi-bin/echo": path
"/opt/oracle/inst/Apache/Apache/logs/fastcgi/dymanic/aac1cec5416b961cf002c5526b4159" 
is too long for a Domain socket

Note:

The FastCGI limit of 108 characters is applicable to Apache 2.0 also.

7.2.2 Oracle HTTP Server Does Not Start After Enabling Port Tunneling or SSL in mod_oc4j

Oracle HTTP Server might not start if you modify its configuration to enable port tunneling (iASPT), or SSL in mod_oc4j. Following are the possible solutions for this issue:

Recommended solution: if mod_perl is not needed, disable it by commenting out the LoadModule perl_module libexec/libperl.so line from httpd.conf.
If mod_perl is needed, ensure that you are running the latest patch set from Sun, and move the LoadModule line for mod_perl until after the include of mod_oc4j.conf in httpd.conf.

7.2.3 Redirects Break If OracleAS Web Cache is Turned Off or is Disabled

By default, Oracle HTTP Server sends redirects to the OracleAS Web Cache listening port. If OracleAS Web Cache is not running or is disabled, then redirects from Oracle HTTP Server (and any OC4J application behind Oracle HTTP Server) will not work. If you are not planning to run OracleAS Web Cache, then edit httpd.conf and ssl.conf, changing the Port directive so that it matches the Listen directive instead of the OracleAS Web Cache listening port.