-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review use of QueryBuilder and prevent ResourceResolver leakage #1539
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@davidjgonzalez I think we should reopen this issue after merging #1686 . The CloseableQueryBuilder should ease mitigation in most places. |
… with CloseableQB.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@adamcin Do you recall where this was left off? I thought you actually ended up going through and updated the uses of QueryBuilder to use CloseableQueryBuilder. Do you recall if you only tackled a subset? |
@davidjgonzalez I believe I converted all usages of QueryBuilder that were present at the time. |
This was fixed w/ CloseableQueryBuilder |
Use of QueryBuilder APIs for querying often results in a leaking ResourceResolver.
The ACS Commons code-base should be reviewed for use of QueryBuilder and any leakage should be mitigated.
The text was updated successfully, but these errors were encountered: