InitialContext#lookup does not timeout

[stianst]

I've got an issue where InitialContext#lookup will hang forever doing a lookup if there is a problem with the network. I appreciate this is the default settings of the TCP sockets to wait forever, so I've tried to configure the timeout using 'jnp.timeout' and 'jnp.sotimeout', but it still waits forever.

Hashtable<String, String> env = new Hashtable<String, String>();
env.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
env.put("java.naming.provider.url", "jnp://10.9.1.11:1099");
env.put("java.naming.factory.url.pkgs", "org.jboss.naming");
env.put("jnp.socketFactor", "org.jnp.interfaces.TimedSocketFactory");
env.put("jnp.timeout", "1000");
env.put("jnp.sotimeout", "1000");

InitialContext ctx = new InitialContext(env);

HelloWorld world = (HelloWorld) ctx.lookup("HelloWorldBean/remote");
world.sayHello("hello");

// disconnect network here

world = (HelloWorld) ctx.lookup("HelloWorldBean/remote");
world.sayHello("hello");

In the above example if the network is disconnected before the first lookup it times out as expected, but if the network is disconnected between the first and the second lookup it doesn't timeout at all (waited 10 min+).

[stianst]

If I disconnect the network between the last lookup and invoking the bean it times out fine, so problem seems to be limited to InitialContext

[jaikiran]

Although not a solution to your problem, there's this one another similar post http://community.jboss.org/message/549274#549274

[ronsen]

env.put("jnp.socketFactor",   -> Factory?

[stianst]

Thanks for your comment. It still doesn't work after fixing that typo though, as neither of "jnp.socketFactory", "jnp.timeout" or "jnp.sotimeout" are used when invoking the naming server. These properties only configure the sockets used to retrieve the stub that is used to invoke the naming server. All the configuration of the stub itself is done on the server and it doesn't seem to be any way of configuring that.

[ronsen]

Hi Stian,

probably this can help resolving your problem: http://community.jboss.org/message/408077

[stianst]

Thanks Ron, but as I said in my previous comment all these properties are only relevant on the socket that is used to connect to the server to retrieve the stub. They do not set anything on the stub itself, which would be fully configured on the server. As far as I can tell there is no timeout set on the socket used by this stub.

In effect that means there is a timeout when retrieveing the stub (i.e. connecting to the naming server), but when using the stub (i.e. doing a lookup) there are no timeouts.

[stianst]

My hope was that this would all be fixed in AS7 but there is no remote JNDI support at all in AS7. So I guess we'll be waiting for 7.1 to see!

Another thing I don't quite understand about the Naming implementation. There is a server socket listening on 1099, all that does is return the stub, while any communication to the Naming server is done through 1090. Why are two ports needed?

[ronsen]

At first, as I checked the AS7, i was also quite disappointed that the JNDI support isnt implemented yet and that there only exists a "hack"-workaround for this, that is quite shaky at all....so, lets wait for 7.1 then.

The reason for the porting can be that these are 2 different modules, but to be honest i have no clue and asked the question my self as well.