We experienced that with jabber for windows (Version 11) the client has more than one (up to 5 or more) tcp connection established to the ldap server (port 389).
In Version 10.6 of the jabber client, we do not see such a behavior. With Jabber client 10.6 only one tcp connection is established per client.
The ldap server has to answer search requests from the jabber client. In my opinion it doesn't make sense, that the jabber client needs more than one established tcp connection to the ldap server.
We have a production environment of about 400 clients and the ldap server has over 1300 established tcp connections on port 389.
Is there maybe a setting to control this behavior?
