Javax.naming.ServiceUnavailableException: Ldapxxxxxxxxx:389; Socket Closed
(Doc ID 2306712.1)
Last updated on SEPTEMBER 13, 2017
Applies to:Oracle Endeca Information Discovery Studio - Version 3.1.0 and later
Information in this document applies to any platform.
Import LDAP contacts through Endeca Studio is throwing error
Customer is getting only approx. 1000 objects per execution of the import job, but they need almost 15000 to be fetched.
Is there some configured limitation they are hitting?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!