[ https://issues.jboss.org/browse/ISPN-7122?page=com.atlassian.jira.plugin.... ] Tuomas Kiviaho commented on ISPN-7122: -------------------------------------- The bad thing is that the slowness can creep in gradually long after the decision to utilize this cache-store has been made. It seems to me based on what is documented into the codebase that in the feat of JPA eager fetch causing OOME, the fetching of only id's is being applied. Hibernate nowadays admits in it's fetching strategies that eager fetch should be disabled by default and (named) entity graphs/queries should be used instead in contradiction what default fetch types of @ManyToOne and @OneToOne are. The code base seems to be still using now deprecated criteria queries, but allowing different fetching strategies would leave the responsibility of avoiding possible OOME to the configurator. When no named entity graphs/queries have been provided then the default behavior could be what it is currently. [~sannegrinovero] What would happen if the https://issues.jboss.org/browse/ISPN-4538 would be solved by just applying detach right after the entity has been consumed. Would it impact also the possible second level cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)