[OPENAM-10427] LDAP connections created by the configurator wizard are never closed Created: 19/Jan/17  Updated: 07/Mar/19

Status: Open
Project: OpenAM
Component/s: configurator
Affects Version/s: 14.0.0, 7.0.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Peter Major [X] (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: AME, Should-Fix
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
is related to OPENAM-14562 GUI configurator sends too many ldap ... Closed
Rank: 1|hzss5z:

 Description   

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.



 Comments   
Comment by Andy Hall [ 23/Jan/17 ]

The fix may be to remove the configurator.

Generated at Sat Feb 27 22:00:21 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.