webMethods Knowlegebase : IS LDAP connections not closed. (1750739)

Problem

The user is going to replace the deprecated flow libraries for LDAP interfacing (WmPublic.pub.ldap:*) with the WmPublic.pub.client.ldap:*

During tests user noticed a mismatch about IS LDAP connection management concerning the disconnect phase.

Extract from the directory server log showing the differences:

The log messages below are produced by a search operation performed by webMethods with the old, deprecated flow services (pub.ldap:connect pub.ldap:search pub.ldap:disconnect):

conn=1632831 op=-1 msgId=-1 - fd=91 slot=91 LDAP connection from 88.8.88.888:1432 to 77.7.77.777

conn=1632831 op=0 msgId=1 - BIND dn="cn=USR_MAN" method=128 version=3

conn=1632831 op=0 msgId=1 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=USR_MAN"

conn=1632831 op=1 msgId=2 - SRCH base="ou=my_base_ou,dc=my_base,dc=my" scope=2 filter="(uid=00000020362)" attrs="dn"

conn=1632831 op=1 msgId=2 - RESULT err=0 tag=101 nentries=1 etime=0

conn=1632831 op=2 msgId=3 - UNBIND

conn=1632831 op=2 msgId=-1 - closing from 88.8.88.888:1432 - U1 - Connection closed by unbind client -

conn=1632831 op=-1 msgId=-1 - closed.

You can see the connection opening, the search operation and the connection closing.

Here he log messages produced during the same search operation performed with the new WmPublic.pub.client.ldap:* flow services (pub.client.ldap:bind pub.client.ldap:search with close=yes):

conn=1632799 op=-1 msgId=-1 - fd=97 slot=97 LDAP connection from 99.9.99.999:64424 to 77.7.77.777

conn=1632799 op=0 msgId=1 - BIND dn="cn=USR_MAN" method=128 version=3

conn=1632799 op=0 msgId=1 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=USR_MAN"

conn=1632799 op=1 msgId=2 - BIND dn="cn=USR_MAN" method=128 version=3

conn=1632799 op=1 msgId=2 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=USR_MAN"

conn=1632799 op=2 msgId=3 - SRCH base="ou=my_base_ou,dc=my_base,dc=my" scope=2 filter="(uid=00000020362)" attrs=ALL

conn=1632799 op=2 msgId=3 - RESULT err=0 tag=101 nentries=1 etime=0

So there are 2 "BIND" ldap operations instead of the expected one, and there are no "UNBIND" or "disconnect" operations, despite the flows are defined to close the connection through the "close" input parameter.

It seems the new flow services are using a kind of "ldap connection pool", but we can't find any reference about its configuration in the user manual.