It happens when we use GenerationType.IDENTITY in parent table and enable batch processing. It happens after version 5.2.15.