8 Oracle HTTP Server

8.1.1 Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle Application Server 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).

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

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