Unfortunately the connection pool that you activated is poorly configured by default and is therefore nearly pooling nothing.
You can re-configure the pool behaviour by jvm system properties that are documented here: http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html . <br/>
These system properties have to
The Java System Properties can be set in the ivy engine launch configuration (*.ILC [jvm.options file][5].
Note: Before 7.4 you need to this in the *.ilc file on windows and in the engine /bin directory). *.conf file for linux. See the [engine guide][1] for ILC reference.
- You can enable the jndi trace logging with the property <br/>
**-Dcom.sun.jndi.ldap.connect.pool.debug=all**
![alt text][2]
- From a pool you might expect that it always re-used already created connections if they are idle. But this pool doesn't. To realy enable this feature i made good experiences by setting the property <br/>
**-Dcom.sun.jndi.ldap.connect.pool.prefsize=-1** ![alt text][3]
- Another reason why your pool might is not working is SSL. SSL connections are for security reasons not pooled by default. If the debug property is enabled you get a clear message with that info. However you can enable SSL connection pooling with the following option. <br/>**-Dcom.sun.jndi.ldap.connect.pool.protocol=ssl** ![alt text][4]
[1]: http://developer.axonivy.com/doc/latest/EngineGuideHtml/misc.html#misc.toolreference.ilc
[2]: http://answers.axonivy.com/upfiles/ldapPool_createDebugMessage-evenWhenConnectionsAreAvailable.png
[3]: http://answers.axonivy.com/upfiles/ldapPool_withNegativePrefSize-tryToReuseIdleConns2.png
[4]: http://answers.axonivy.com/upfiles/ldapPool_disabledForSSL2.pnghttp://answers.axonivy.com/upfiles/ldapPool_disabledForSSL2.png
[5]: https://developer.axonivy.com/doc/latest/engine-guide/configuration/files/jvm-options.html
