I am having an issue using HA JNDI. My issue is with the timeout of a lookup. Here is the scenario:
1. 2 machines active
2. A client is started and does a lookup.
3. 1 of the machines is disconnected from the network (the network cable is pulled).
4. The next lookup the client performs takes a long time, ~90 seconds.
Is there someway to change the timeout on the lookup? I have tried the jnp.sotimeout and the jnp.timeout properties, but I think I have the same issue as the following post with the cache:
Has anyone seen this before? I am using JBoss 4.0.2.
I found what I was looking for, I should have looked a bit closer at the InitialContext. I closed the old context (which cleared the default/cache) and recreated it when I loose connection. After that, lookups "fail" when I want them to...