-
1. Re: JNDI timeout problem from client
joelvogt Jul 10, 2002 10:55 PM (in response to dudgeon)try localhost as provider url not 127.0.0.1
-
2. Re: JNDI timeout problem from client
dudgeon Jul 11, 2002 5:50 AM (in response to dudgeon)That's what I tried first with no success!
Tim -
3. Re: JNDI timeout problem from client
jwkaltz Jul 11, 2002 6:15 AM (in response to dudgeon)> 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) -
4. Re: JNDI timeout problem from client
dudgeon Jul 11, 2002 6:26 AM (in response to dudgeon)Tried that as well!
Tim -
5. Re: JNDI timeout problem from client
jwkaltz Jul 11, 2002 7:17 AM (in response to dudgeon)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
- ...? -
6. Re: JNDI timeout problem from client
dudgeon Jul 11, 2002 7:41 AM (in response to 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