My Oracle Support Banner

Enterprise Manager Returns HTTP-404 After JDeveloper Installed into Same Middleware_Home as FMW (Doc ID 1349812.1)

Last updated on JUNE 30, 2023

Applies to:

Oracle Fusion Middleware - Version and later
Information in this document applies to any platform.


The FMW Products 11.1.1.x and JDeveloper have all been installed using the same middleware home.  After JDeveloper was installed, now logging into the Enterprise Manager page http://<HOSTNAME>.<DOMAIN>:<PORT>/em returns the following errors:

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication
is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client,
the status code of 403 (Forbidden) can be used instead. The 410 (Gone)
status code SHOULD be used if the server knows, through
some internally configurable mechanism, that an old resource is permanently
unavailable and has no forward address

The AdminServer.log shows the following errors:

####<DATE TIME> <Error> <Deployer> <host> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <ECID> <VALUE> <BEA-149205> <Failed to initialize the application 'em' due to error java.lang.ClassNotFoundException: javax.faces.application.ProjectStage.
java.lang.ClassNotFoundException: javax.faces.application.ProjectStage
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(


FMW Products 11.1.1.x and JDeveloper are all installed into the same Middleware_Home.


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.