Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Microsoft Windows x64 (64-Bit)

Part Number E14774-41
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

10 Oracle HTTP Server

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

10.1 Configuration Issues and Workarounds

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

10.1.1 OHS Fails to Start When mod_perl is Enabled on Microsoft Windows x64 (64-Bit) 2008

In 11.1.1.5.0 release, Oracle HTTP Server (OHS) installation is successful with OHS start and stop working fine on Microsoft Windows x64 (64-Bit) 2008. But OHS fails to start when mod_perl is enabled by copying

%ORACLE_INSTANCE%\config\OHS\ohs1\disabled\mod_perl.conf

to

%ORACLE_INSTANCE%\config\OHS\ohs1\moduleconf

The console shows the following error:

Process (index=1,uid=2032669523,pid=6444) time out while waiting for a managed
process to start.

To work around this issue, perform the following steps:

  1. Complete Oracle Fusion Middleware 11g R1 Patch Set 1 (11.1.1.2.0) and 11g R1 Patch Set 4 (11.1.1.5.0) installation.

  2. Go to My Oracle Support:

    https://support.oracle.com
    
  3. Click the Patches & Updates tab.

  4. Enter patch 12316692 in the Patch Name or Number field, under Patch Search.

  5. Click Search.

  6. Download and apply the patch by following the instructions in the README file included with the patch.

10.1.2 Oracle HTTP Server Fails To Load mod_wls module on Windows 64-Bit Server Systems

On x64 edition systems of Microsoft Windows Server 2003 R2 and Microsoft Windows Server 2008 R2, Oracle HTTP Server fails to load the mod_wl_ohs module if the MatchExpression property is provided within the IfModule weblogic_module block of the mod_wl_ohs.conf file.

To workaround this issue, comment out the MatchExpression property inside the IfModule weblogic_module block.

For example

<IfModule weblogic_module>
       WebLogicHost <hostname>
       WebLogicPort ....
       Debug ON
       WLLogFile .......
       # MatchExpression *.*
       </IfModule>