Skip Headers
Oracle® Application Server Release Notes
10g (9.0.4) for Solaris Operating System (SPARC)
Part No. B10629-15
  Go To Documentation Library
Home
Go To Table Of Contents
Contents

Previous
Previous
Next
Next
 

10 Oracle HTTP Server

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

10.1 General Issues and Workarounds

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

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

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

10.1.3 Enabling mod_oprocmgr

You must have at least one non-https port enabled for Oracle HTTP Server in order to enable mod_oprocmgr.

10.2 Configuration Issues and Workarounds

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

10.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).

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

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

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

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

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

10.3 Documentation Errata

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

10.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 the OC4J section of the Oracle Application Server 10g Release Notes and the Oracle Application Server Containers for J2EE User's Guide.

10.3.2 Configuring Anonymous Access for IIS

In the "Using Oracle Application Server Containers for J2EE Plug-in" appendix of the Oracle HTTP Server Administrator's Guide, add the following information to configure anonymous access for IIS:

Perform the following steps if you want OC4J to perform the authentication:

  1. In the IIS Management GUI, right click on the default Web site and select Properties.

  2. Select the Directory Security tab and click the Edit button under Anonymous Access and Authentication Control. Be sure that the Anonymous access is checked and that basic authentication and integrated Windows Authentication are both unchecked.


Note:

If you want IIS to perform authentication and simply pass the user name to OC4J, then do not disable authentication in IIS.

10.3.3 Errors in Steps for Configuring OC4J Plug-in on Sun ONE

"Configuring OC4J Plug-in on Sun ONE" section in "Using Oracle Application Server Containers for J2EE Plug-in" appendix of the Oracle HTTP Server Administrator's Guide contains the following errors:

  1. Add the following lines at the end of /sunone/https-mymachine/magnus.conf:

    Init fn="load-modules" shlib="/sunone/opii.so" funcs=oppi_init,opii_objecttype,opii_service,opii_child_init
    
    

    should read:

    Init fn="load-modules" shlib="/sunone/opii.so" funcs=opii_init,opii_objecttype,opii_service,opii_child_init
    
    
  2. Make the following modifications to /sunone/https-mymachine/obj.conf:

    1. Add the following line before any ObjectType line:

      ObjectType fn=opii_objecttype
      
      
    2. Add a Service line, such as:

      Service Type="oracle/opii" fn="opii_service" UserOutPutStreamSize = 8192
      
      

    should read:

    1. Add the following line before any ObjectType line:

      ObjectType fn=opii_objecttype
      
      
    2. Add a Service line, such as:

      Service type="oracle/opii" fn="opii_service"
      
      

      Note:

      You may need to use UseOutputStreamSize to optimize performance. Refer to Sun ONE Web Server documentation for details.

10.3.4 Error in Steps for Configuring Sun ONE Listener to Use Proxy Plug-in

Step 4 in "Configuring Sun ONE Listener to Use Proxy Plug-in" section in "Using Oracle Application Server Proxy Plug-in" appendix of the Oracle HTTP Server Administrator's Guide contains the following error:

Add the following line to the <Object name=default> section of the obj.conf file, before all other lines beginning with the word ObjectType:

ObjectType fn=op_objecttype UserOutputStreamSize=8192

should be

Add the following line to the <Object name=default> section of the obj.conf file, before all other lines beginning with the word ObjectType:

ObjectType fn=op_objecttype

10.3.5 Remove "Not Supported By Oracle" Note for Modules

"Oracle HTTP Server Modules" chapter of the Oracle HTTP Server Administrator's Guide states that the following modules are not supported by Oracle:

mod_asis

mod_auth_dbm

mod_cern_meta

mod_example

mod_imap

mod_log_agent

mod_nmap_static

These modules are supported by Oracle.