-8176553
Thanks,
Jan Kalina
diff --git a/src/java.naming/share/classes/com/sun/jndi/ldap/AbstractLdapNamingEnumeration.java b/src/java.naming/share/classes/com/sun/jndi/ldap/AbstractLdapNamingEnumeration.java
--- a/src/java.naming/share/classes/com/sun/jndi/ldap/AbstractLdapNamingEnumeration.java
ceptions()) &&
+ ! (errEx instanceof LimitExceededException)) {
if (homeCtx.handleReferrals == LdapClient.LDAP_REF_THROW) {
throw (NamingException)(refEx.fillInStackTrace());
------
Thanks,
Jan Kalina
Note: Test is not included, as it would require running LDAP server.
(existing ldap tests in JDK use only mocks of the server)
The patch was manually verified using reproducer attached to issue.
On Wed, Apr 4, 2018 at 4:12 PM, Jan Kalina <jkal...@redhat.com> wrote:
> Hi,
> I has prep
definitely, while LimitExceededException is EXPECTED,
but it does not occur.
On Wed, Apr 4, 2018 at 5:35 PM, Vyom Tewari <vyom.tew...@oracle.com> wrote:
>
>
> On 4/4/2018 8:59 PM, Jan Kalina wrote:
>>
>> Note: Test is not included, as it would require running LDAP server
Just note the LDIF expect the LDAP server running at:
ldap://localhost:10389/dc=example,dc=com
The "ref" needs to reference the same server to create referrals loop.
If you are unable to reproduce, does it produce LimitExceededException for you?
On Wed, Apr 4, 2018 at 6:05 PM, Jan Ka
