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

Memory leak in PartTreeJpaQuery after upgrade from 2.1.9 to 2.2.2 #19546

Closed
kgunnerud opened this issue Jan 6, 2020 · 2 comments
Closed

Memory leak in PartTreeJpaQuery after upgrade from 2.1.9 to 2.2.2 #19546

kgunnerud opened this issue Jan 6, 2020 · 2 comments
Labels
for: external-project For an external project and not something we can fix

Comments

@kgunnerud
Copy link

We bumped spring boot from 2.1.9 to 2.2.2 not so long ago, and right after that we started getting OOMs from time to time ( 7-8 times a day).
After downloading the heap-dump a few times through the actuator endpoint, I see that the memory gets filled with items in ConcurrentHashMap under PartTreeJpaQuery.QueryPreparer.

No special config except for:

spring.jpa:
    open-in-view: false
    properties.hibernate:
      generate_statistics: true
      query:
        plan_cache_max_size: 64
        plan_parameter_metadata_max_size: 32

and dependency for spring-boot-starter-data-jpa.

After checking the issues under milestone 2.2.0, 2.2.1 and 2.2.2, I see 2x upgrades of Hibernate but no other mentions.

I checked spring-data-jpa, found no special changes there lately that should have had this effect.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 6, 2020
@mbhave
Copy link
Contributor

mbhave commented Jan 6, 2020

PartTreeJpaQuery` is part of Spring Data which uses JIRA for issue tracking. If you'd like to discuss the problem with the Spring Data team, please open a JIRA ticket.

@mbhave mbhave closed this as completed Jan 6, 2020
@mbhave mbhave added for: external-project For an external project and not something we can fix and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 6, 2020
@kgunnerud
Copy link
Author

Great, thanks. The issue has already been reported there I see and a fix is in PR if anyone else wonders about this: spring-projects/spring-data-jpa#402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: external-project For an external project and not something we can fix
Projects
None yet
Development

No branches or pull requests

3 participants