Port Number In Weblogiccluster Parameter Specified In Httpd.Conf Is Not An Integer Less Than 65535 (Doc ID 1379651.1)

Last updated on JUNE 11, 2015

Applies to:

Oracle Discoverer - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to start Discoverer Viewer or Plus using the Webcache or OHS port the following message is returned:

Failure of server APACHE bridge:
Port number in WebLogicCluster parameter specified in httpd.conf is not an integer less than 65535, or servers are not specified correctly. Cannot continue.


If DebugConfigInfo parameter is switched on, in the generated file the following can be seen:

Tue Nov 22 12:18:48 2011 <70413219571281> The final request string is '/discoverer/viewer'
Tue Nov 22 12:18:48 2011 <70413219571281> parseServerList: Socket Address hostnames '<host_name>'
Tue Nov 22 12:18:48 2011 <70413219571281> parseServerList: could not resolve any valid WLS hostname specified in the static list
Tue Nov 22 12:18:48 2011 <70413219571281> parseServerList failed to parse the id. Returning NULL
Tue Nov 22 12:18:48 2011 <70413219571281> *******Exception type [CONFIG_ERROR] (Port number specified in WebLogicCluster parameter specified in httpd.conf is not an integer less than 65535, or servers are not specified correctly) raised at line 2089 of ap_proxy.cpp

Changes

In ORACLE_INSTANCE/config/OHSComponent/ohs-comp-name/moduleconf/module_disco.conf, WebLogicPort directive was introduced.
Specifically, in section

<IfModule mod_weblogic.c>
<Location /discoverer>


WebLogicCluster <host_name>:9002
was replaced with:

WebLogicCluster <host_name>
WebLogicPort 9002

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms