Bug 1017111 - LDAP context mis-close in LDAPIdentityStoreImpl
Summary: LDAP context mis-close in LDAPIdentityStoreImpl
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: PicketLink
Version: 5.2.2.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Boleslaw Dawidowicz
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-09 09:32 UTC by Toshiya Kobayashi
Modified: 2018-12-03 20:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1017119 (view as bug list)
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PLIDM-44 0 Major Resolved LDAP context mis-close in LDAPIdentityStoreImpl 2014-07-21 08:43:26 UTC

Description Toshiya Kobayashi 2013-10-09 09:32:06 UTC
Platform BZ for https://issues.jboss.org/browse/PLIDM-44

Steps to reproduce: Please see "Steps to Reproduce:" in PLIDM-44

Comment 1 JBoss JIRA Server 2013-10-09 09:53:13 UTC
Tom Fonteyne <tfonteyn> made a comment on jira PLIDM-44

It's the line:

  ldapCtx.unbind(jndiName);

which appears twice in that class, that should be removed. An unbind explicitly says to close the connection, instead of simply putting it back in the pool.

Comment 3 JBoss JIRA Server 2013-10-14 15:52:04 UTC
Marek Posolda <mposolda> updated the status of jira PLIDM-44 to Resolved

Comment 4 JBoss JIRA Server 2013-10-14 15:52:04 UTC
Marek Posolda <mposolda> made a comment on jira PLIDM-44

Fixed by commit https://github.com/picketlink/picketlink-idm/commit/90624614537c560b0df6b296c0c901c932468056


Note You need to log in before you can comment on or make changes to this bug.