Back to bug 1017119
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Boleslaw Dawidowicz | 2013-11-04 08:27:55 UTC | Doc Text | Cause: In some situations LDAP connections are not released properly Consequence: Size of connection pool is increasing Workaround (if any): Result: May lead to exceeded LDAP connection pool | |
| Doc Type | Bug Fix | Known Issue | ||
| Jiri Pallich | 2013-11-13 15:17:42 UTC | Target Release | --- | 6.1.1 |
| CC | jpallich | |||
| Thomas Heute | 2013-11-14 09:29:59 UTC | Status | NEW | ASSIGNED |
| CC | theute | |||
| Boleslaw Dawidowicz | 2013-11-19 09:13:09 UTC | Whiteboard | FixAval | |
| Boleslaw Dawidowicz | 2013-11-19 09:20:55 UTC | Whiteboard | FixAval | FixAvail |
| Boleslaw Dawidowicz | 2013-11-20 09:17:56 UTC | Priority | unspecified | medium |
| Boleslaw Dawidowicz | 2013-11-26 10:54:35 UTC | Target Milestone | --- | DR01 |
| Peter Palaga | 2013-11-26 21:51:20 UTC | Status | ASSIGNED | ON_QA |
| CC | ppalaga | |||
| Tomas Kyjovsky | 2013-12-18 16:24:15 UTC | Status | ON_QA | ASSIGNED |
| CC | tkyjovsk | |||
| Thomas Heute | 2013-12-18 16:27:52 UTC | Target Milestone | DR01 | ER01 |
| Tomas Kyjovsky | 2013-12-18 16:48:14 UTC | Status | ASSIGNED | VERIFIED |
| Target Milestone | ER01 | DR01 | ||
| Jared MORGAN | 2014-02-04 22:37:45 UTC | CC | bdawidow | |
| Doc Text | Cause: In some situations LDAP connections are not released properly Consequence: Size of connection pool is increasing Workaround (if any): Result: May lead to exceeded LDAP connection pool | CAUSE: A duplicated ldapCtx.unbind(jndiName); in LDAPIdentityStoreImpl caused the LDAP connections to not be released properly in some situations. CONSEQUENCE: This caused the size of the connection pool to increase, and can lead to the LDAP connection pool to be exceeded. FIX: RESULT: | ||
| Doc Type | Known Issue | Bug Fix | ||
| Flags | needinfo?(bdawidow) | |||
| Boleslaw Dawidowicz | 2014-02-10 08:14:07 UTC | Doc Text | CAUSE: A duplicated ldapCtx.unbind(jndiName); in LDAPIdentityStoreImpl caused the LDAP connections to not be released properly in some situations. CONSEQUENCE: This caused the size of the connection pool to increase | CAUSE: A duplicated ldapCtx.unbind(jndiName); in LDAPIdentityStoreImpl caused the LDAP connections to not be released properly in some situations. CONSEQUENCE: This caused the size of the connection pool to increase |
| Doc Text | , and can lead to the LDAP connection pool to be exceeded. FIX: RESULT: | , and can lead to the LDAP connection pool to be exceeded. FIX: There is a fix in Picketlink IDM 1.4.4.Final to ensure that LDAP connections are opened just in case when needed and they are all properly closed after finish their work. RESULT: No | ||
| Doc Text | more connections leaks in LDAP connection pool | |||
| Flags | needinfo?(bdawidow) | |||
| Jared MORGAN | 2014-02-11 05:19:31 UTC | Doc Text | CAUSE: A duplicated ldapCtx.unbind(jndiName); in LDAPIdentityStoreImpl caused the LDAP connections to not be released properly in some situations. CONSEQUENCE: This caused the size of the connection pool to increase, and can lead to the LDAP connection pool to be exceeded. FIX: There is a fix in Picketlink IDM 1.4.4.Final to ensure that LDAP connections are opened just in case when needed and they are all properly closed after finish their work. RESULT: No more connections leaks in LDAP connection pool | It was discovered that in certain scenarios, a duplicated ldapCtx.unbind(jndiName); in LDAPIdentityStoreImpl caused LDAP connections not to be released properly. This caused the size of the connection pool to increase, and could have lead to the LDAP connection pool exceeding it's upper size limit. The fix implements enhancements to Picketlink IDM 1.4.4.Final, which opens LDAP connections in case they are required and closes the threads correctly after work completes. This fixes the originally reported connection leaks in the LDAP connection pool. |
| PnT Account Manager | 2019-01-01 03:40:25 UTC | QA Contact | dpospisi | tkyjovsk |
Back to bug 1017119