In my application I see most of the memory used by hibernate is on QueryImpl class and the query retrieves data from sample employee class. I use getResultSet to retrieve the resultset. When there is concurrent request, the allocation increases without releasing the memory though request is complete…

What you see there is probably the objects that haven’t been collected by the JVM GC, but the proble might be that you are fetchcing more data than necessary. Try using DTO projections because they are more efficient both on the database and on the client side. More, if you have huge Result Sets b…

Thank you Vlad. I followed DTO projection implementation from your performance guide book and while implementing I noticed this error. Can you please help. [image] Query specified join fetching, but the owner of the fetched association was not present in the select list Hibernate O…

QueryImpl consuming more memory

Hibernate ORM

shiva February 21, 2018, 6:20am 3

Thank you Vlad. I followed DTO projection implementation from your performance guide book and while implementing I noticed this error. Can you please help.

Topic		Replies	Views
Query specified join fetching, but the owner of the fetched association was not present in the select list Hibernate ORM	17	40884	December 21, 2018
Java request taking 40-50MB memory Hibernate ORM	8	3124	March 30, 2018
Hibernate too much memory Hibernate ORM	4	1309	April 12, 2018
Query.getResultStream() throws OOM Hibernate ORM	0	1426	September 21, 2019
Why hibernate make so much queries even while using DTO and LAZY LOADING? Hibernate ORM	1	270	March 15, 2024

QueryImpl consuming more memory

Related topics