JNDI timeout problem from client

[dudgeon]

I'm new to jBoss, so please bear with me!

Having succesfully deployed an EJB, it's now time to test it from a simple client. However I'm getting problems with doing jndi lookups, as I don't seem able to get a JNDI connection. The appropriate bit of code is as follows

Properties env = new Properties();
env.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
env.put("java.naming.factory.url", "127.0.0.1:1099");

// Get a naming context
InitialContext jndiContext = new InitialContext(env);

// Get a reference to the Bean
Object ref = jndiContext.lookup("families/Family");

...


The error I get is

javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]

I can telnet to port 1099 from a terminal window and get garbage back that suggests rmi stuff is in operation on that port.

I've got jboss-j2ee.jar and jnp-client.jar on my classpath.
Using jBoss3.0 and JDK1.4

Any solutions would be welcome!

Thanks

Tim

[joelvogt]

try localhost as provider url not 127.0.0.1

[dudgeon]

That's what I tried first with no success!

Tim

[jwkaltz]

> env.put("java.naming.factory.url",
> "127.0.0.1:1099");

I've got "jnp://host:port" ... don't know if that makes a difference (it doesn't if jnp is the default protocol, but I don't know about that)

[dudgeon]

Tried that as well!

Tim

[jwkaltz]

If you're running under Unix, use the following to see if the JBoss naming service is really up and running :
lsof -i | grep 1099

Possible connection problems could be,
- jboss naming didn't start successfully, because something else is already on the default port 1099
- you can't access the port 1099 on the intended machine because there is a firewall or some other access restriction
- ...?

[dudgeon]

Nailed it.

It was a wrongly secified property in the InitialContext's environemnt. Should have been

java.naming.provider.url not java.naming.factory.url
or better still
Context.PROVIDER_URL
which would have avoided all the problems in the first place.

Thanks to all.

Tim