[hibernate-issues] [JIRA] (HHH-15524) Entity with bytecode enhancement is being re-initalized on lazy-load causing reset of parent dirty tracking

Ben Ganley ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5fc058e... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzlkNTk3Yjc3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15524?atlOrigin=eyJpIjoiYzlkNT... ) HHH-15524 ( https://hibernate.atlassian.net/browse/HHH-15524?atlOrigin=eyJpIjoiYzlkNT... ) Entity with bytecode enhancement is being re-initalized on lazy-load causing reset of parent dirty tracking ( https://hibernate.atlassian.net/browse/HHH-15524?atlOrigin=eyJpIjoiYzlkNT... ) Issue Type: Bug Affects Versions: 5.6.11 Assignee: Unassigned Attachments: image-20220919-092433.png, image-20220919-092454.png, image-20220919-092511.png, image-20220919-092529.png Components: bytecode-enhancement Created: 19/Sep/2022 02:28 AM Environment: Hibernate 5.6.11.Final Java 18 Postgres 13 Priority: Major Reporter: Ben Ganley ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5fc058e... ) Experiencing issues where after updates to a Hibernate entity, no updated data is being flushed to the database. After some debugging, traces show that lazy-loading an entity is causing the entity to be re-initialized, clearing any fields marked as dirty. Prior to lazy-load of relation After to lazy load of relation Trace from lazy load We have currently worked around this issue in our code base by calling either Hibernate.initialize() or eager loading this relation for the services its needed. ( https://hibernate.atlassian.net/browse/HHH-15524#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15524#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100207- sha1:7afd384 )