Use the attached byteman script on one node of a 2 or more node cluster. JAVA_OPTS=-javaagent:$BYTEMAN_HOME/lib/byteman.jar=script:/path/to/pauseHARMIServerImplinit.btm (This script just pauses at the right spot to make it easier to trigger the bug. Without the script, just restart one member of the cluster repeatedly while hitting HA-JNDI until the timing is just right to trigger it). Start the other member(s) of the cluster except for the one with the byteman script. From a standalone client configured with jndi.properties to hit HA-JNDI, run: InitialContext context = new InitialContext() while ( true ) context.lookup ( ... ); Start the member with the byteman script.

In previous EAP 5 releases some clients saw <literal>NullPointerException</literal> when calling HAJNDI during startup. This was cause by <literal>HARMIServerImpl</literal> processes requests for HAJNDI before it is fully initialized. This would produce errors from components that were not in the correct state. As a resolution to this issue, <literal>HARMIServerImpl</literal> now throws <literal>java.rmi.NoSuchObjectException</literal> if a request comes in during startup, which causes an automatic retry in the client HAJNDI code.