5
Oracle HTTP Server

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

• Section 5.1, "General Issues and Workarounds"

• Section 5.2, "Configuration Issues and Workarounds"

• Section 5.3, "Documentation Errata"

5.1 General Issues and Workarounds

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

• Section 5.1.1, "OC4J Plug-in Usage with Standalone and Core Installation"

• Section 5.1.2, "Limited Concurrent Use of mod_oc4j and mod_jserv"

• Section 5.1.3, "Limitation of C/tcsh Shell"

5.1.1 OC4J Plug-in Usage with Standalone and Core Installation

To use the OC4J plug-in with the OC4J standalone product without OPMN, only static routing to specific hosts and ports is allowed within the OC4J plug-in, and OC4J must be configured to use AJP. Using static routing with hosts and ports means that only Oc4jMount directives such as the following are supported:

Oc4JMount /j2ee/* ajp13://localhost:6001,localhost:6002

To enable AJP in the OC4J configuration, a line such as the following must be present in the default-web-site.xml file in the OC4J configuration:

<web-site port="3000" protocol="ajp13" display-name="OracleAS Java Web Site">

where the port value specifies the port that this OC4J process will listen on for incoming AJP requests.

5.1.2 Limited Concurrent Use of mod_oc4j and mod_jserv

Since both mod_oc4j and mod_jserv route requests for servlet containers, care must be taken when configuring both to run within a single Oracle HTTP Server instance. In particular, avoid using the mod_jserv directive ApjServAction as it might create routing issues. For example, if the use of this directive involves mapping all requests ending in .jsp, then requests that were meant to be serviced by OC4J through an Oc4jMount directive might be routed unsuccessfully to mod_jserv.

5.1.3 Limitation of C/tcsh Shell

If the default shell is C (csh) or tcsh, the opmnctl stopall command will not work as expected. Change the default shell to the Korn (ksh) , Bourne (sh) or Bash (bsh) shell to workaround this issue. This problem is caused by a known limitation of the C and tcsh shell on Linux systems.

5.2 Configuration Issues and Workarounds

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

• Section 5.2.1, "Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle Application Server (9.0.4.x)"

• Section 5.2.2, "Manually Editing mod_plsql Configuration Files"

• Section 5.2.3, "Invalid mod_plsql Configuration Files Do Not Appear in Oracle Enterprise Manager Interface"

• Section 5.2.4, "FastCGI Sockets Path Length Error"

• Section 5.2.5, "Oracle HTTP Server Does Not Start After Enabling Port Tunneling or SSL in mod_oc4j"

• Section 5.2.6, "ApJServManual setting Information for Enabling mod_jserv"

5.2.1 Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle Application Server (9.0.4.x)

Oracle does not support using 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 10g (9.0.4.x). 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 (9.0.4.x). Use mod_proxy to route data between Oracle HTTP Server component supplied with Oracle9iAS Release 1 (1.0.2.2.x) andOC4J supplied with Oracle9iAS Release 1 (1.0.2.2.x).

5.2.2 Manually Editing mod_plsql Configuration Files

If you edit the mod_plsql configuration files ORACLE_HOME/Apache/modplsql/conf/dads.conf or ORACLE_HOME/Apache/modplsql/conf/cache.conf then you must follow these steps to synchronize DCM and Oracle Enterprise Manager:

• Run the $ORACLE_HOME/dcm/bin/dcmctl -updateConfig -co HTTP_Server on the command line.

• Restart Application Server Control, so that the mod_plsql administration in Oracle Enterprise Manager can pick up the changes.

• Restart Oracle HTTP Server to pick up the changes to the configuration files.

5.2.3 Invalid mod_plsql Configuration Files Do Not Appear in Oracle Enterprise Manager Interface

If you are using Application Server Control to configure mod_plsql files and upon further examination the files are corrupt or contain invalid syntax, there will be no configuration data displayed in Oracle Enterprise Manager. No configuration operations are performed.

5.2.4 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 123.123.123.123] [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/aac1cec5416b961cf002c5526b4
159" is too long for a Domain socket

5.2.5 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.

5.2.6 ApJServManual setting Information for Enabling mod_jserv

When enabling mod_jserv, the ApJServManual directive works in "off" mode only when Apache is started using apachectl start, and not opmnctl.

5.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

• Section 5.3.1, "Additional Metric-based Load Balancing Information"

5.3.1 Additional Metric-based Load Balancing Information

The "Oracle HTTP Server Modules" chapter of the Oracle HTTP Server Administrator's Guide contains information about metric-based load balancing. For additional information on the topic, refer to Chapter 8 and the Oracle Application Server Containers for J2EE User's Guide.