JNDI naming exception in JRE7

Question

We are faced with a problem, we have the base code in JDK 6. Now we are switching to JRE-7. Which ultimately means that we are running code compiled in JDK-6 with JRE -7. Everything works fine except for JNDI. We get the following exception.

2015-05-25 09:44:41,769 ERROR ne.LdapNeNotifListener - NamingExceptionEvent recieved from ABC: javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms. at com.sun.jndi.ldap.Connection.readReply(Connection.java:483) at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:639) at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:607) at com.sun.jndi.ldap.LdapCtx.getSearchReply(LdapCtx.java:1919) at com.sun.jndi.ldap.LdapNamingEnumeration.getNextBatch(LdapNamingEnumeration.java:129) at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:216) at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(LdapNamingEnumeration.java:189) at com.sun.jndi.ldap.NamingEventNotifier.run(NamingEventNotifier.java:134) at java.lang.Thread.run(Thread.java:745) 

As we can see, the wait time is -1, therefore, it is infinite according to JAVA documents. Not sure what causes the problem here.

Any help would be appreciated.

Answer 1

I just downloaded and tested the JRE version 7u80.

Everything works great here. I have not seen any exceptions.

This is a JRE version lower than or equal to 7u79, which is causing problems.

Answer 2

Yes, it works with the latest version of JRE version 7u80. It is also noted that this error occurs only when working with bulk data.

Has anyone noticed the same usecase?

Answer 3

Could this be a problem? Oracle says it's fixed in 7 updates 91, but I can’t say for sure. The authorization date and other backups were made at about the same time as your report. http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8081560