I'm missing something that is likely brutally obvious - I'm hoping someone
can slap me with the answer :>)
I've built and deployed several EJBs - I used the sample EJB client from the
documentation as a test client. This client works fine when running on the
same machine as jboss.
I then move to another machine - I've changed the jndi.properties file to
include the IP of the jboss server (and I've tried its name, etc as well).
I'm getting this exception:
javax.naming.CommunicationException [Root exception is
java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested
exception is:
java.net.ConnectException: Connection refused: connect]
The 127.0.0.1 part is a bit confusing - here's the jndi.properties file
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=172.168.0.3
java.naming.factory.url.pkgs=org.jboss.naming
My first thought was that the jndi.properties file was not being found -
however if I STOP jboss on the server, I get this exception:
javax.naming.ServiceUnavailableException: Connection refused:
connect [Root exception is java.net.ConnectException: Connection refused:
connect]
And, if I change the IP address in the jndi.properties file to a
non-existent IP, I get
javax.naming.ServiceUnavailableException: Operation timed out:
connect [Root exception is java.net.ConnectException: Operation timed out:
connect]
So, it sure seems like I have the correct jndi.properties file. I know that
port 1099 is active on the server - if I telnet there, i get lots of
garbage, including the text java.rmi.... What am I missing? I'm using the
jboss.jcml from the tomcat configuration directory - all mbeans appear to
start correctly during initialization. I'm running jboss on Mandrake Linux
8.1, and the test application on Windows 2000. Thanks! Ian
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
