My Oracle Support Banner

HTTP-404 Page Not Found When Accessing OracleAS 10.1.3 ASControl and BPEL Consoles Via Remote HTTP Server (Doc ID 429519.1)

Last updated on JUNE 28, 2021

Applies to:

Enterprise Manager for Fusion Middleware - Version to
Oracle HTTP Server - Version to [Release AS10gR3]
Oracle Fusion Middleware - Version to [Release AS10gR3]
Information in this document applies to any platform.
Oracle HTTP Server - Version: to
Enterprise Manager for iAS - Version: to
This problem can occur on any platform.


The objective is build an OracleAS 10.1.3 distributed cluster topology with two or more OracleAS 10.1.3 instances. The intention is separate the HTTP Server into its own Oracle Home and/or machine i.e

Machine 1: OracleAS 10.1.3 J2EE Server instance (this instance may or may not have SOA Suite)
Machine 2: OracleAS 10.1.3 Web Server instance (Oracle HTTP Server only install)

The OracleAS 10.1.3 J2EE Server instance has been chosen at install time to be the administration instance and therefore contains the AS Control application.

When attempting to access, via the HTTP Server on Machine 2, any of the consoles like AS Control or, if using SOA Suite, BPEL Console, ESB Console, WSM Console,  the browser returns a 404 error.

For example, if Oracle HTTP Server is listening on port 7777


works fine and returns the HTTP Server Welcome page

The AS Control url



Page cannot be found

(No login dialogue is shown, the browser just reports back "404 Page Not Found")

The consoles can, however, be accessed via the J2EE OC4J lightweight listener which exist as part of the OracleAS 10.1.3 J2EE instance on Machine 1.

For example the OC4J lightweight listener may listening on port like 8889.


These urls work fine.


At install time, the OracleAS 10.1.3 J2EE Server was designated as the Adminstration Instance, BUT

- a Basic install type was chosen
- an Advanced Install Type was chosen but the options in the "'Cluster Topology Configuration" dialogue screen were left unchecked

This may have been due to a mistake or misunderstanding on the part of the administrator performing the build.

Or another scenario is that the business may have only decided to have a remote Oracle HTTP Server, as a front end to the J2EE Server, after the installation of J2EE Server was complete. It's possible that the administrator then attempted to change the architecture post install by following the advice given in the documentation below

Oracle Application Server Administrator's Guide 10g Release 3 (
Chapter 6 Reconfiguring Application Server Instances
Chapter 6.2.1 Configuring a Web Server and OC4J on Separate Hosts

This advice worked fine and a simple servlet, deployed in the J2EE Server instance, can be accessed via the remote HTTP Server. Yet the console applications, like AS Control, remain inaccessible.


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

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