Bug 795856 - The result of failed LDAP query should not be cached
Summary: The result of failed LDAP query should not be cached
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.2.1.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 5.2.2.ER01
Assignee: Boleslaw Dawidowicz
QA Contact:
URL:
Whiteboard:
Depends On: 830081
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 16:35 UTC by bkramer
Modified: 2018-11-27 20:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 10:58:30 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description bkramer 2012-02-21 16:35:05 UTC 
Description of problem:

Currently, it can happen that if finalResults object (in LDAPIdentityStoreImpl.java) was first initialized inside of try{} block and then Exception happened during LDAP query, it could result in storing such failed result. 

Code in LDAPIdentityStoreImpl.java should be improved to include additional logging and make sure that nothing gets cached in case when LDAP query fails.


Version-Release number of selected component (if applicable):


How reproducible:

** It's not easy to reproduce, but when it happens, it's always in clustered environment.
Comment 1 hfnukal@redhat.com 2012-06-06 11:22:56 UTC 
Upgrade Picketlink to at least 1.1.10
Comment 2 Boleslaw Dawidowicz 2012-06-20 10:58:30 UTC 
This issue is hard to reproduce and verify however it is likely to assume that PicketLink IDM 1.1.10 upgrade fixes it.
Note You need to log in before you can comment on or make changes to this bug.