[markoh]

Hmm...
Sorry, I unzip now clean version of Jboss and try once more.
It works with ./run.sh -Djboss.bind.address=myhost.com
But nothing halpful with JAVA_OPTS in run.conf

Thanks.

But now one more problem - how to shutdown Jboss now?
I found on this forum advice to use this parameter, but it also doesn't work:
./shutdown.sh -Djava.naming.provider.url=jnp://myhost.com:1099 -S

[test]

It's not working for me ..... and I don't see why it should be a Network Problem as it's working fine with others version and I'm still on the same machines !!!!!

[test]

I've tryed all your advice, nothing seems to work for me .... if somebody knows some configuration secrets to solve this very basic problem .... I'll appreciate

[javajedi]

IKTH, but I'm having the exact same problem.

JBoss 3.2.2
Mandrake Linux 2.4.21-0.13mdk
JDK 1.4.2_01

server.log excerpt:
INFO [org.jboss.mq.il.uil2.UILServerILService] JBossMQ UIL service available at
: tarantula/192.168.1.125:8093

client log excerpt:
TRACE Nov 25 17:20:51 [UILServerIL.java] - Connecting to : /0.0.0.0:8093

Somewhere along the way it looks like a bug is telling the client to connect to address 0.0.0.0 for the UIL2 service.

Here's my server's /etc/hosts file:
127.0.0.1 localhost
192.168.1.125 tarantula.hmsonline.com tarantula

Any pointers would be greatly appreciated. Thanks.

--Tim

[javajedi]

Turns out I had set the jboss.bind.address on 1 of the 2 machines in the cluster, and was pointing to it from the client side, but it must have redirected me at the other server in the cluster, because once I set the jboss.bind.address on the other server, everything started working. This should still probably be filed as a bug if it hasn't been already. You shouldn't have to manually set jboss.bind.address just to get this to work, especially if there is only 1 address on the machine.

[adrian.brock]

FYI

I have fixed the problem in CVS

http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/il/uil2/UILServerILService.java?r1=1.1.4.3&r2=1.1.4.4

This caters for /0.0.0.0 and 0.0.0.0/0.0.0.0

It should be availble in 3.2.3 which is due out soon
(current plan is this weekend).

Regards,
Adrian

[thoennes]

Adrian, quoting the change you made

40 public static String getSpecificBindAddress()
41 {
42 String address = System.getProperty(ServerConfig.SERVER_BIND_ADDRESS);
43 ejort 1.2 if (address == null || address.equals(ANY))
44 return null;
45 return address;
46 }

I cannot see were you check for "/0.0.0.0" or "0.0.0.0/0.0.0.0" if ANY is defined as "0.0.0.0"

In addition, how does this stuff works in case of multiple physical or virtual interfaces? We got the same error as in this
thread and configured -Djboss.bind.address=XXX.

In our setup is XXX a virtual address. After starting the server,
netstat shows that all servives listen at this address, but if a JMS client connects remotely, it first contacts RMI, but then tries to connect to a different address, namely the physical address of this host.

If I got it right from glancing at the source (unfortunately there was no JMS track in the JBoss Advanced Training ;), the
client first contact RMI successfully at the right address, but RMI does not tell the client the bind address, but the physical address of the JMS service.

We did not have this problem with 3.0.8, so there might be a change in the way JBoss handles these bind addresses?

Regards, Joerg

[adrian.brock]

-Djava.rmi.server.hostname

Regards,
Adrian

[thoennes]

Thanks, we will try this. Could you explain in more detail, were this property comes into play, e.g. how is the detailed scenario if a client contact a JMS provider?

Actually, we did some experiments in the meantime and
enables both the TRACE log level for org.jboss.mq and did
some network snoops.

I must confess that I understand the issue now much better (this does not mean "fully"), e.g. the "/0.0.0.0" seems to be the toString() format of InetAddress and the quoted source was wrong (should be fixRemoteAddress). For the moment we rolled back to RC2 which seems to work.

A possible workaround for us was to use

run.sh -Djboss.bind.address=""

i.e. the empty string. After that, some services listened at localhost, but others (as JMS) were fine and returned a working IP address. So a workaround for 3.2.2 would be to use

run.sh -Djboss.bind.address="" \
-Djboss.bind.address2="0.0.0.0"

and adapt the XML files accordingly.

If we use virtual interfaces as the bind address, the server always returns the physical address (InetAddress.getLocalHost()).

But I would except to return something like

ServerSocket rmiSocket;
Socket clientSocket = rmiSocket.accept();

InetAddress localHostToUse =
clientSocket.getLocalAddress();

This also works for multi-homed hosts and virtual interfaces.
Consider the case, that the physical address is 192.168.x.x
or is blocked by a firewall. Then the client successfully contacts RMI, but then gets an unroutable or blocked IP address.

How about the Binding Manger? Does it solve some of these problems?

Cheers, Joerg

P.S. Why does this forum software does not accept German umlauts?!?!

[jdwn]

Hello,

I've tried several possible sollutions, but none of them worked. When I start my jboss, I still see the 0.0.0.0 jboss bind address coming up, even when I set -Djboss.bind.address="". I also tried several thngs like myhost.com.

Can somebody help? Is there somebody that solved this problem and knows how to set jboss.bind.address and what to enter there?

Thnx

[fdubru]

Hi,

I had the same connection problem. A simple way to (temporarily) solve it is to switch to RMI invocation layer.

[thoennes]

Hi both,

As Adrian mentioned above, the fix is in the CVS.

And it is released with JBoss 3.2.3. We have tested it and it
works fine for us.

So please do not ask for workarounds, but just upgrade to 3.2.3.
As far as I can see there are no major changes, only bug fixes.

Cheers, Joerg