Customer may see extra active TCP connections in LDAP Adapter 6.1 when they upgrade their project from older version 5.4.
This usually happens when the project has a request response service with multithreading enabled. For example in a project that has request response service with JMS transport, the thread number of DefaultJMSQueueSession in multithreading TAB is set to 16, customer could see more than 32 active established connections to LDAP server when BW application sends request
to the service. While in 5.4 version, the active connections is about 16 or less. This could cause concerns and problems if customer has a limited
TCP connection resource.

An enhancement request ALDP-890 is created for this issue to remove the extra TCP connections. Please see the Jira ticket for details.
 

Extra Active TCP connections to LDAP server in LDAP Adapter 6.1

The workaround is to lower the thread number per transport session (for example DefaultJMSQueueSession) in multithreading TAB, it will not remove the
extra connections but can reduce the total connections number. The number of total active TCP connections is about 2*(thread number) + Number of other adapter services(sub, pub).