Well, in this particular version we’re still on Hibernate 4.3… I’m already working on the migration to 5.2.
I am sure in this old codebase, there is something wrong with the session handling 
In this code, it was started e.g. to execute many session.updates() as the concept of dirty checking has not been understood correctly. There was also manual session handling like openSession instead of using getCurrentSession()… Probably it will just work in the updated code base that removed all the strange session stuff, but still we have to deal with product applications running on the old version.
Regarding the improved logging: you’re right, pull request is in preparation