Hibernate LazyInitializationException after Session close

LazyInitializationException when accessing lazy association after Hibernate Session.close()

0 reputation · 20 Apr 2024, 21:38 UTC

13.9K views0

The goal is to return entity data from a public REST endpoint without accidentally initializing uninitialized Hibernate proxies or exposing associations outside the transaction that loaded them.

Hibernate throws LazyInitializationException when a lazy association is accessed after its Session is closed. Setting hibernate.enable_lazy_load_no_trans permits loading outside a transaction, but it does not restore transactional isolation and may issue additional SQL unexpectedly. Serializing a managed entity directly in an HTTP response can trigger proxy initialization during serialization, which may cause failures or unintended database reads. Behavior may differ between Hibernate 5.x and 6.x; confirm against the target version.

Should the application rely on hibernate.enable_lazy_load_no_trans to allow post-close access, or is a DTO projection required to control serialization? Does JSON serialization of an entity with uninitialized proxies risk accidental data exposure after the Session is closed?

Keep exploring this topic

DetachedInstanceError when accessing lazy-loaded relationship after session close

Investigating whether DetachedInstanceError after session close indicates a performance bottleneck: correlation with lazy-load latency, instrumentation, and session configuration trade‑offs.

Jhipster REST Controllers vs Hibernate Lazy Loading: Diagnosing Deployment Failures from Logs

Jhipster deployments with Hibernate lazy loading can fail silently, logging only a generic 500 error. Identify which association triggers the LazyInitializationException, map it to the REST endpoint, and discover logging patterns that reveal the offending field.

Hibernate + Spring Data JPA: Lazy Loading Across Transaction Boundaries

Explores whether Hibernate should return empty collections for detached lazy associations instead of throwing LazyInitializationException when used with Spring Data JPA.

Global vs. Per‑Route Serialization in Fastify: Which Approach Yields Better Performance for High‑Throughput APIs?

Choosing between a global schema‑based serializer and per‑route default serialization in Fastify raises questions about startup overhead, runtime performance, error handling, and plugin encapsulation for high‑throughput APIs.

`hibernate.enable_lazy_load_no_trans` only relaxes lazy loading for an open Session running without a transaction. After `Session.close()`, the entity is detached, so accessing an uninitialized lazy proxy or collection still throws `LazyInitializationException`; the flag cannot reopen the Session or restore isolation.

For REST responses, project to a DTO inside the transaction and fetch only required associations. Serializing a managed entity directly lets the JSON mapper invoke getters after close, risking failure or partial payloads. Hibernate 5.x (`javax.persistence`) and 6.x (`jakarta.persistence`) differ, so verify behavior against the target version.

Practical check: load an entity, commit and close the Session, then access a lazy getter outside the transaction and assert `LazyInitializationException`. Enable SQL logging to confirm no implicit SELECT fires after close.

LazyInitializationException when accessing lazy association after Hibernate Session.close()

0 answers

Your perspective belongs here.

1 question comment