Embedded OC4J's RMI Server Does Not Listen On Logical Interface of the Host
(Doc ID 403868.1)
Last updated on APRIL 04, 2022
Applies to:
Oracle Containers for J2EE - Version 9.0.4.1.0 to 10.1.3.1.0 [Release AS10g to AS10gR3]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
A logical networkinterface (ipge0:1) with a separate IP address is configured on the machine.
But the RMI-Server of the OC4J embedded in Oracle Application Server only listens on the
loopback and physical interface.
$ netstat -an | grep 12459
<IP_1>.12459 *.* 0 0 49152 0 LISTEN
127.0.0.1.12459 *.* 0 0 49152 0 LISTEN
where 12459 is OC4J RMI Port.
$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ipge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet <IP_1> netmask ffffff00 broadcast 10.0.0.255
ipge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet <iIP_2> netmask ffffff00 broadcast <IP_3>The host can be pinged successfully on both ipaddresses - <IP_1> and <IP_2>
Changes
Multiple interfaces are configured on the machine.
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 |
| Oracle Application Server 10.1.3.x |
| Oracle Application Server 9.0.4.x and 10.1.2.x |
| References |