In class org.jnp.interfaces.NamingContext:
1) When NamingContext.lookup() is called the lookup is
done in a loop that is *always* executed MAX_REPEAT
(==10) times. The result of naming.lookup(n) is not
checked in the loops condition clause.
The problem leads to no error, but decreases performance.
2) When the lookup fails MAX-REPEAT times, there is no
proper exception handling. IMHO the catched
ConnectException should be thrown.
The bugs were found in JBoss 3.0.4. The second one is
fixed in 3.1beta2, but the first still exists.
Logged In: YES
user_id=175228
Both issues have been fixed in all cvs branches.