Skip to content
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

#3173 - BeanSet lazy loading / Too many DataSource connections used #3203

Merged
merged 1 commit into from
Aug 29, 2023

Conversation

rbygrave
Copy link
Member

  • The error reported was that a DataSource connection pool maxed out
  • The symptom was that there was an additional lazy loading queries invoked via the hashCode/equals implementation of ManyToMany Set.
  • The fix is for BeanSet init() to lazy load with onlyIds = false, that avoids the extra lazy loading query from being executed

- The error reported was that a DataSource connection pool maxed out
- The symptom was that there was an additional lazy loading queries invoked via the hashCode/equals implementation of ManyToMany Set.
- The fix is for BeanSet init() to lazy load with onlyIds = false, that avoids the extra lazy loading query from being executed
@rbygrave rbygrave self-assigned this Aug 29, 2023
@rbygrave rbygrave added the bug label Aug 29, 2023
@rbygrave rbygrave linked an issue Aug 29, 2023 that may be closed by this pull request
@rbygrave rbygrave merged commit 0d69377 into master Aug 29, 2023
@rbygrave rbygrave deleted the feature/3173-BeanSet branch August 29, 2023 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Datasource connection deadlock
1 participant