I ran into the following problem with HA-JNDI:

I am using my own InitialContextFactory implementation, that will create a HA-JNDI context with an empty URL if the code is running outside JBoss and with the URL of the HA-JNDI when running inside JBoss. The factory is just a wrapper over org.jnp.interfaces.NamingContextFactory, modifying the URL depending on the environment (inside / outside JBoss) ant it works just fine.

I have some code that does bind / lookup operations using this factory, and I have witnessed inconsistencies of the HA-JNDI.

Example:
code running outside JBoss listing the HA-JNDI:
#--satellites

code running inside JBoss listing the HA-JNDI:
#--satellites
#--ss-jndi

This problem has occurred often, but not every time. The two bindings ar there prior to running the code. I have encountered similar inconsistency problems with code running on different (clustered) JBoss instances, although the partition information is correct.

What is the problem, is it in my code or is this a JBoss problem ? I am using JBoss 3.0.6 .