The problem still exists in Hibernate 4.3.5. Please reopen the ticket. Seems as this ticket is a duplicate to HHH-8583,