Force Binding to a Specific IP Address For the RMI Port Results in the Error: "This OC4J Is Configured To Make JMX Connections Via RMIS And Fall Back To RMI If The RMIS Port Is Not Configured"
(Doc ID 423411.1)
Last updated on AUGUST 15, 2022
Applies to:
Enterprise Manager for Fusion Middleware - Version 10.1.3.0.0 to 10.1.3.2.0Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.2.0 [Release AS10gR3]
Information in this document applies to any platform.
Symptoms
When trying to configure an OC4J Container to bind to a specific IP address for the RMI protocol in a multi-network card system, the application becomes inaccessible. For example, the ASControl console will not show the authentication screen. It will show the following error message instead:
This OC4J is configured to make JMX connections via RMIS and fall back to RMI if the RMIS port is not configured.
The RMIS connection on the OC4J instance home on Application Server is configured but a connection could not be established.
The JMX proto is specified by the oracle.oc4j.jmx.internal.connection.proto property in opmn.xml
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 |
| References |