We're performing an upgrade to our application to latest hibernate version, it still contains this issue.

Can this be re-opened?