Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux Itanium and Linux Itanium
B15871-05
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

6 Oracle HTTP Server

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

6.1 General Issues and Workarounds

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

6.1.1 OC4J Plug-in Usage with Standalone and Core Installation

To use the Oracle Application Server Containers for J2EE (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. OC4J must be configured to use Apache JServ Protocol (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">



In this example, where the web-site port value specifies the port at which the OC4J process will listen for incoming AJP requests.

6.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It contains the following topic:

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

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

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