-
1. Re: JB3.2.1 JNP doesn't seem to handle multiple network card
ioparra Oct 23, 2003 4:42 PM (in response to ioparra)After scavenging through the open rmi source code, it appears that the Card A is being picked up from the RMI port. I essentially this while telnetting directly to the port(I'm hoping this output will escape correctly):
$ telnet 107.51.51.107 1099 (Card B)
Trying 107.51.51.107...
Connected to 107.51.51.107.
Escape character is '^]'.
192.168.1.1rmMarshallejecojfcxConnection closed by foreign host. ~ UnicastRef2rver.RemoteObjectOaa3
Later, the app tries to connect to 192.168.1.1(card A).
This is the source of the problem, anyone know how to change that?
-Ivan -
2. Re: JB3.2.1 JNP doesn't seem to handle multiple network card
juha Oct 23, 2003 5:05 PM (in response to ioparra)Can you try it with 3.2.2 and RmiBindAddress attribute?
module: src/main/org/jboss/naming; files: NamingService.java
comments: Add the RmiBindAddress attribute for the RMI Naming service bind address.
-- Juha -
3. Re: JB3.2.1 JNP doesn't seem to handle multiple network card
ioparra Oct 23, 2003 5:35 PM (in response to ioparra)Juha-
Tried it straight from source and still no good.
the only configuration I set was the:
Port 1055
BindAddress <Card A>
RmiBindAddress <Card A>
After telnetting into CardA:1055, I still see Card B IPAddress in the output. :(
I run my test case and it still shows Card B at SYNC_SENT state.
It was worth the try.
-Ivan -
4. Re: JB3.2.1 JNP doesn't seem to handle multiple network card
juha Oct 23, 2003 7:04 PM (in response to ioparra)Ok,
can you file a bug report on sourceforge.
-- Juha -
5. Re: JB3.2.1 JNP doesn't seem to handle multiple network card
ioparra Oct 28, 2003 3:15 PM (in response to ioparra)So if anyone ever has the same problem, the fix is passing setting "java.rmi.server.hostname" property before starting jboss.
-
6. Re: JB3.2.1 JNP doesn't seem to handle multiple network card
hakucho Mar 28, 2004 8:26 PM (in response to ioparra)Thanks ioparra, I found the same bug and your workaround fixed it for me! Hopefully it will be fixed in a future release of JBoss?
Andrew