JB3.2.1 JNP doesn't seem to handle multiple network cards

[ioparra]

Here is my scenario:

Jboss3.2.1 with 2 Nic Cards(A,B).
I specified the JNDI BindAddress to Card B.

From a completely seperate machine:
If I connect to card B on the JNDI port, I get the initial context. But the lookup does the call on card A. Card A, of course, is unaccessible from any other network.

I tried setting the jnp.localAddress field in the jndi.properties, still no good.

If you telnet to Card B at the JNDI Port, I get Marshall junk AND the ip-address of Card A.

I look through the stack trace and the lookup and see that NamingContext only has Card B information. But when this context calls getServer(), it returns the ip address of card A.

Any suggestions out there on how to solve/avoid this.

-Ivan

[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

[juha]

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

[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

[juha]

Ok,

can you file a bug report on sourceforge.

-- Juha

[ioparra]

So if anyone ever has the same problem, the fix is passing setting "java.rmi.server.hostname" property before starting jboss.

[hakucho]

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