Steps to reproduce:
- On the configurator wizard complete the forms until the user data store settings
- Be very slow when you fill out the details of the user store connections (especially when entering the password)
- Each time the wizard sends an AJAX request to OpenAM, OpenAM will create a new monitored LDAP connection factory
By tailing the DJ access logs you should be able to see a new BIND request every single second corresponding to each connection failure. This is because the getConnection call from AjaxPage only returns the connection, not the actual factory. Later on both Step3 and Step4 closes the connection but the underlying connection factory is never actually closed.
The only way to stop the invalid connection attempts (and the connection leak) is to restart the container after configuration.