My Oracle Support Banner

Activate Changes Hangs Or Goes To Internal Link When Using mod_wl_ohs Proxy With or Without SSL (Doc ID 1358674.1)

Last updated on JUNE 30, 2023

Applies to:

Oracle Fusion Middleware - Version 11.1.1.4.0 to 11.1.1.5.0 [Release Oracle11g]
Information in this document applies to any platform.

Symptoms


The goal is to configure the Weblogic plugin in HTTP Server, and thereafter setup SSL termination on the hardware load-balancer, and to allow access to the admin server via port 443 from the outside. Following the standard setup documentation all seems to work fine in the Admin Console, except for the button to "Activate Changes" - this hangs and does not return. 

Even without SSL, Once a different outside host and port is set up , Activate Changes can hang.
 
Using a HTTP Sniffing tool, it will be noticed that "Activate Changes" is trying to go to the old internal hostname and port.

Changes

A typical configuration scenario is as follows:
------------------------------------------------------
1) A hardware load-balancer is in front of a Weblogic domain, with each managed server/admin server fronted by HTTP server.
  The proxy plugin is configured identically in the front-end HTTP Server instances.

2) Adminserver running at <Hostname>.<Domain>:<NonSSLPort>

3) The LB name for OHS is <FrontendHostname>.<Domain>:<SSLPort>

4) The relevant entry in mod_wl_OHS.conf is :

 <Location /console>
     SetHandler weblogic-handler
     WebLogicHost <Hostname>.<Domain>
     WeblogicPort <NonSSLPort>
     WLProxySSL ON
     WLProxySSLPassThrough ON
 </Location>

5) In the Admin server , the protocol / http is set to :

FrontendHost <FrontendHostname>.<Domain>
FrontendHttpPort 0
FronntendHttpsPort <SSLPort>

6) The settings for admin server / General

listen Address:  <Hostname>.<Domain>   <NonSSLPort>
SSL is not enabled
WLSProxy plugin ticked


7) The setting for admin Server : HTTP  :
frontend host:  <FrontendHostname>.<Domain>   port 0  ssl port <SSLPort>


8)  httpd.conf setup as follows :
Listen <OHSPort>
ServerName <InternalHostname>.<Domain>
NameVirtualHost *:<OHSPort>
<VirtualHost *:<OHSPort>>
    ServerName https://<FrontendHostname>.<Domain>:<SSLPort>
    RewriteEngine On
    RewriteOptions inherit
</VirtualHost>

9) mod_wl_ohs entries :
 # Admin Server and EM
 <Location /console>
     SetHandler weblogic-handler
     WebLogicHost <Hostname>.<Domain>
     WeblogicPort <NonSSLPort>
     WLProxySSL ON
     WLProxySSLPassThrough ON
     DebugConfigInfo ON
 </Location>
 
 <Location /consolehelp>
     SetHandler weblogic-handler
      WebLogicHost <Hostname>.<Domain>
     WeblogicPort <NonSSLPort>
     WLProxySSL ON
     WLProxySSLPassThrough ON
 </Location>


10) In addition, the new 10.3.4 WLS plugin requirements have been implemented; see Note 1316142.1  "How To Configure mod_wl_ohs with Oracle HTTP Server and Oracle WebLogic Server " which talks of the new requirements for 10.3.4+ when using MOD_WL_OHS or another plugin and indeed all plugin-based SSL configs, the requirement being setting the "WLS plugin" checkbox to "enabled."
This will be done for both admin and domain.
 
- - - - - - - - - - - - - - - - - - - - - - - - - - -
 
At this point, the admin console login via https://<FrontendHostname>.<Domain>/console is successful and all functions work

except activate changes

 
 
 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.