Michael Kroll ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62ea4af... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiZDI5NT... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiZDI5NT... ) This seems to happen in combination with {code:java} @DynamicUpdate @OptimisticLocking(type = OptimisticLockType.DIRTY) {code} This i found by debugging: In our case {{ writtenFieldNames }} and writtenValues only contains the changed field and its new data as single entries, but the changed field is found in the attributeMapping on a bigger index. Then, this bigger index is used to access writtenValues. The misconception in this code here is that {{ writtenFieldNames }}, writtenValues and the attributeMapping are of the same size and order, which they are not. I am not sure why this goes away when disabling dynamic update and optimistic locking. ( https://hibernate.atlassian.net/browse/HHH-16577#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16577#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#100234- sha1:9e2db29 )