7 Replies Latest reply on May 31, 2003 10:46 PM by jonlee

can not connect to jboss 3.0.6 from remote client

pstrotmann May 20, 2003 7:24 AM

Hi all,

connecting to the server with a client running on the same physical machine (192.168.0.1) as the server works fine (thank you JonLee):

gp-client:
[gp] GpClient started
[gp] new InitialContext() successful
[gp] jndi.lookup('gp/GpController') successful
[gp] gpControllerHome.create() successful
[gp] Anzahl Gps zu Strot,443 : 2
[gp] Anzahl Gps zu Strot, : 3
[gp] gpCtl.remove() successful

BUILD SUCCESSFUL

to run the client I used ant:

After installing the client on another computer (192.168.0.2) using the same ant control (except changing localhost to 192.168.0.1, the name of the remote machine I get:

gp-client:
[gp] GpClient started
[gp] new InitialContext() successful
[gp] jndi.lookup('gp/GpController') not successful
javax.naming.communication.exception. root exception is java.rmi.connect.exception: connection refused to host: 127.0.0.1;
nested exception is: java.net.connectException is: Connection refused

the physical connection between the computers by ping works in both directions. Did I use a wrong syntax spe
cifying the remote computer or is there some serversided configWork necessary to allow the access to the server ?

peter

1. Re: can not connect to jboss 3.0.6 from remote client

vbatista May 26, 2003 10:29 AM (in response to pstrotmann)

Hello!
I am having the same exception:

javax.naming.communication.exception. root exception is java.rmi.connect.exception: connection refused to host: 127.0.0.1;

I am running JBoss-3.2.1 with bundled Tomcat 4.1.24.

When I execute my Remote Session Beans between 2 Win2000 machines, everything runs ok. I only have problems when the client is on one of the Win machines, and the server is on a RedHat 9.0 box.

I can connect successfully with the server on a Win machine and the client on the RedHat machine.

Any help would be welcome.

Thanks in advance,
Victor Batista
Actions
2. Re: can not connect to jboss 3.0.6 from remote client

askesis May 26, 2003 12:48 PM (in response to pstrotmann)

Depending on what you did during installation RedHat Linux creates a /etc/hosts file that does not work with JBoss. If your host file contains:

127.0.0.1 yourhostname yourhostname.yourdomain localhost.localdomain localhost

then change that into

127.0.0.1 localhost.localdomain localhost
your.ip.addres yourhostname yourhostname.yourdomain
Actions
3. Re: can not connect to jboss 3.0.6 from remote client

vbatista May 26, 2003 2:37 PM (in response to pstrotmann)

Hello!
Thanks for your reply!
I have changed the /etc/hosts file according to your post, but unfortunately I still have the same error!

What can the problem be?

Thanks in advance,
Victor Batista
Actions
4. Re: can not connect to jboss 3.0.6 from remote client

askesis May 26, 2003 3:59 PM (in response to pstrotmann)

Are there any IPChains rules inplace that prohibit the W2K client to connect to the Linux server?
Actions
5. Re: can not connect to jboss 3.0.6 from remote client

vbatista May 30, 2003 2:10 PM (in response to pstrotmann)

Hi!
Thanks for your reply.
Unfortunately there is no firewall between the two machines. Do you have any idea of what the problem can be?

Thanks in advance,
Victor Batista
Actions
6. Re: can not connect to jboss 3.0.6 from remote client

jonlee May 31, 2003 9:50 PM (in response to pstrotmann)

Have your tried running the client from RedHat and does that work?

Also, the order of declaration is important in the /etc/hosts file. Declare the simple name first before the FQDN.

127.0.0.1 localhost localhost.localdomain
192.168.1.1 frodo frodo.hobbiton.com
Actions
7. Re: can not connect to jboss 3.0.6 from remote client

jonlee May 31, 2003 10:46 PM (in response to pstrotmann)

One other thing to note; the line entry for your server name must match the value returned when you type:
hostname.

All of this is not a requirement of JBoss. It is the requirement underlying Java networking and this is specific to the underlying operating system as Java has to determine networking information from the OS.
Actions

Go to original post