Application Deployed In An 10.1.3.5 OC4J Container Is Not Accessible For 30 Minutes After Restart
(Doc ID 1461256.1)
Last updated on OCTOBER 07, 2022
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.
Symptoms
OHS 10.1.3.5
OAS 10.1.3.5 - OC4J Container
64bit Linux
Architecture:
Client --> OHS -->OC4J
Following a restart of the OHS Server, any URL that is for the Application that is deployed on the OC4J container, and is accessed through the OHS Server is unavailable for approx 20-30 minutes.
The OHS Server is unaware of the oc4j process.
Looking at the output from the command opmnctl @cluster debug it can be seen that ONS only sees one node in the cluster:
Any URL that is access directly on the OC4J container works as expected during that time.
Changes
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 |