Getting HTTP 404 Error when Accessing an Application Deployed in a new OC4J Instance in OAS 10.1.3.1.0 Basic Install
(Doc ID 422432.1)
Last updated on FEBRUARY 18, 2025
Applies to:
Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
When using the Basic installation of OAS 10.1.3.1.0, you cannot access the application deployed in the newly created second OC4J instance.
The application deployed in the default 'home' OC4J works fine.
What Works
The application deployment to the second OC4J instance is successful without any errors.
The deployed application is shown in the Enterprise Manager.
Error
When you try to access the application deployed in the second OC4J instance using an URL in the following format:
http://<host>:<port>/<context root>/
where,
<port> is the HTTP server port of the default 'home' OC4J instance.
<context root> is the context root of the application deployed in the second OC4J container.
You see the HTTP 404 - File not found error
Changes
This occurs in OAS 10.1.3.1.0 basic install.
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 |