Resolved issues are described in the following table:
Issue | Description | Reported In OHS Version |
---|---|---|
Create |
If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory |
12.1.2.0.0 |
Creating Instance Named adminserver Throws Exception |
If you try to create an instance with the name adminserver, Oracle HTTP Server throws an exception post after which you will not be able to create instances, even if they have valid names. Therefore, do not attempt to create instances that use the same name as a given administration server. |
12.1.2.0.0 |
SSLWallet Directive in |
When updating the SSL wallet in Fusion Middleware Control, the SSLWallet directive in |
12.1.2.0.0 |
Create Log Directory Manually When Diagnosing Startup Failures |
If an Oracle HTTP Server instance does not start and has not been started before, manually create the directory |
12.1.2.0.0 |
WebLogic Plug-in Enabled option incorrectly described as a checkbox. |
The WebLogic Plug-in Enabled option on the server and cluster pages was incorrectly described as a checkbox in earlier releases of Using Oracle WebLogic Server Proxy Plug-Ins. The WebLogic Plug-in Enabled option is actually a drop-down list containing three items. For more information, see Prerequisites for Configuring the WebLogic Proxy Plug-In. |
12.1.3.0.0 |
Incorrect location of the |
The section Configuring Oracle HTTP Server WebGate for Oracle Access Manager in Installing and Configuring Oracle HTTP Server incorrectly listed the path to the |
12.1.3.0.0 |