The ldap server is active directory 2016. The code that is using the directory ldap api is from a tomcat .WAR (apache guacamole) [1]. I forked [1] and customized the jira/234 PR to support ldap and nginx websocket load balancing in this repo [2] according to apache guacamole's documentation. I'm using docker swarm to set up an overlay network between an nginx reverse proxy to two separate apache guacamole tomcat servlets. The nginx reverse proxy nginx.conf file is provided here [3].
You're correct that userX log entries are successful ldap login attempts that I do to the tomcat .WAR and then I immediately logout and back in another time until the error occurs. What would be causing the handshake to not end? [1] https://github.com/apache/guacamole-client [2] https://github.com/michaelbarkdoll/guacamole-client/tree/jira/234 [3] https://gist.github.com/michaelbarkdoll/d78614635fa0432ab08100d05f1a4919 Michael Barkdoll On Fri, Apr 26, 2019 at 12:26 AM Stefan Seelmann <m...@stefan-seelmann.de> wrote: > On 4/26/19 7:09 AM, Emmanuel Lecharny wrote: > >> ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context > >> > >> java.lang.NullPointerException: null > >> at > >> > >> > org.apache.directory.ldap.client.api.LdapNetworkConnection.connect(LdapNetworkConnection.java:689) > > > > > > It seems, from the code, that the connection times out. The NPE is > > infortunate -and we will fix it- but it’s just masking the real cause: > the > > handshake never ends. > > > > What is the scenario you are running? > > Especially, which LDAP server do you use? > > In error3.txt and error4.txt I see multiple logs messages "User "userX" > successfully authenticated". Does that mean in those cases the > connection to LDAP worked and it only fails randomly? It seems there are > multiple threads involved, so maybe it's a concurrency issue... > > > > >
