[MGNLLDAP-74] Release connection properties when it's not needed Created: 23/Jan/13  Updated: 27/Mar/13  Resolved: 23/Jan/13

Status: Closed
Project: LDAP Connector
Component/s: None
Affects Version/s: 1.4
Fix Version/s: 1.4.5

Type: Bug Priority: Critical
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLLDAP-59 Leak cause ConnectionFactory.connecti... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

During validation user we generate unique connection name and then we save ldap properties into connectionPropertyList map for this connection name. But we don't release this ldap properties when validation is done. So "connectionPropertyList" map still growing and we never clean it.



 Comments   
Comment by Milan Divilek [ 23/Jan/13 ]

This issues doesn't affect to master (1.5.x) branch where connectionPropertyList map doesn't exist.

Generated at Mon Feb 12 02:21:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.