I have added a stacktrace. This stacktrace occurred while running Hibernate 5.1, although I have seen the same behavior in 5.0.