Announcement Announcement Module
Collapse
No announcement yet.
Why LDAP throws CommunicationException even if nothing seems wrong? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Why LDAP throws CommunicationException even if nothing seems wrong?

    Using Spring LDAP 2.0.1, I have the following configuration:

    Code:
    <ldap:context-source id="tf_3ci"
                    url="ldap://${tf.ldap.host}:${tf.ldap.port}" username="anonymous"
                    password="doyoucare" anonymous-read-only="true" >
                    <ldap:pooling max-active="50" 
                        min-idle="1" 
                        test-while-idle="true"
                    />
            </ldap:context-source>
    Everything runs fine for a while, but then it starts throwing CommunicationException left and right:

    Code:
    c.s.p.i.r.LdapServiceClassRepository: Connection reset; nested exception is javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name 'ou=dev,dc=example,dc=com': Connection reset
    I did a tcpdump and saw nothing wrong on the wire; TCP connections were up, and the remote LDAP server was sending responses. I suspected the ldap : pooling invalidated the connections prematurely. Did I miss something in the configuration, or is it more like a bug?

    Thanks
Working...
X