spring-projects / spring-projects/spring-ldap
Missing data from get all users in 2.3.2
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 375
- Forks
- 501
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 63
Description
We are experiencing an issue that appears to be related to the threading/pooling in versions after 2.0.1. We have 2 ldap sources (one is an ldap provider that holds 5000 users, the other is AD that holds 3000 users). We have a gui that allows the user to "browse" all users -- returning the user name followed by a count of memberOf: John A. Doe - (12). The text is created in the Controller where we loop through all the users returned from our query of each source. Something strange is happening. Intermittently, the ldap source returns all the user names with "(0)" accesses. Less frequently, the results from AD are outright missing blocks of users -- some are there, but not all. I could maybe see that the AD results could be from some sort of timeout, but the ldap results are very strange. Any ideas?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the all-users query against both LDAP sources with versions 2.0.1 and 2.3.2, focusing on the Controller loop and the threading or pooling behavior described. Compare complete user blocks and memberOf counts across runs. Done means identifying the cause of missing users or zero counts and confirming consistent results from both sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100