External JNDI access to JBoss 3.0.0

[dweil]

Hi all,

I've deployed an EAR on JBoss 3.0.0, containing a few EJBs. When I try to use these EJBs from a Java application running on the sam hardware box like JBoss, JNDI lookups fail with the exception 'javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]'.
This happens with configuration 'default'; it works with configuration 'all'.

How can I enable JNDI access to JBoss 'default' ?

Dirk

[schaefera]

This seems to be a network problem. Does jndi.properties point to the right server, can this server be accessed (firewall etc.), can you ping and tracert it ?

I doesn't make any sense with respect to different server configurations because the relevant parts are the same (except you changed them).

Also check that you set RmiPort when behind a firewall (and punch a whole in the firewall as well) and set the BindAddress if you have a multi-homed server.

Andy

[ronster]

you may need something like this (at the start of your application)

System.setProperty("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
System.setProperty("java.naming.provider.url",
"jnp://localhost:1099");
System.setProperty("java.naming.factory.url.pkgs",
"org.jboss.naming:org.jnp.interfaces");

[dweil]

The java.naming.provider.url parameter was commented out in jndi.properties. After setting it to jnp://localhost:1099 my app runs with both configurations, 'all' and 'default'.

Thanks so far, but allow 2 more questions:

- what is the default for java.naming.provider.url ?
- why does a JNDI connect/lookup succeed without this parameter with config 'all', but fail with 'all' ?

Dirk