This is really weird ... switching back to LDAP API now works *and* ADS is able to display the default schema, which wasn't working yesterday.
BTW, it is OpenLDAP that I'm connecting to and, yes, it is via LDAPS. I had switched back to -M8 since that continued to work without problems. I'll switch back again to -M10 and see how I get on with that. If it gets stuck again, I've got the JDK installed now and I'll give you the thread dump. Regards Philip On 20 January 2016 at 19:57, Stefan Seelmann <m...@stefan-seelmann.de> wrote: > On 01/19/2016 10:25 AM, Philip Colmer wrote: >> Switching to JNDI *does* fix the problem. > > Could you tell me which LDAP server you try to connect to? Is it Active > Directory? And are you connecting via LDAPS? > > If possible, can you switch back to Apache LDAP API, make it stuck > again, and create a thread dump? To create a thread dump you need a to > have the JDK installed. Then from commandline you can first use "jps" to > get PIDs of Java processes, then use "jstack <pid>" to generate the > thread dump. I just want to know if it gets stuck while communicating > with the server, or if some Studio code is the cause. > > I'm asking because Radovan found an issue with Mina (the framework we > use in LDAP API) that describes your problem[1]. > > Kind Regards, > Stefan > > [1] > https://mail-archives.apache.org/mod_mbox/directory-dev/201601.mbox/%3C569FD0EC.8050203%40evolveum.com%3E > >
