HTTP 404 Error When Deploying Application With The Same Name And Different Context Root On Different OC4J Instances
(Doc ID 747830.1)
Last updated on FEBRUARY 12, 2019
Applies to:Oracle HTTP Server - Version 10.1.3.1.0 to 10.1.3.4.0 [Release AS10gR3]
Information in this document applies to any platform.
This problem can occur on any platform.
Checked for relevance on 13-May-2009
When deploying a J2EE application with different context roots on different containers, using the same application name, application requests result in HTTP 404 errors.
J2EE application has been deployed with the same name and different context root name on different OC4J instances.
The default-web-site.xml file in instance OC4J1 contains the following entry for this application:
The default-web-site.xml file in instance OC4J2 contains a similar entry for this application but with different context root:
When trying to access these applications:
the request is routed to the wrong OC4J instance and HTTP 404 error is received.
After doing a reload/refresh in the browser, the page is rendered correctly in the browser.
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