It seems that Hibernate 4.3.1 introduced a bug. I create the connection in my application with:



but even if the createEntityManagerFactory method fails with an exception, the service registry remains open. However, as you could see from the above code, I cannot terminate my application because as the method didn't succeed the variable connection wasn't assigned (it is null), so I cannot call connection.close() that would destroy the service registry. It seems that this is really a bug, because how will I be able to release resources without resorting to a hack, like using specific Hibernate APIs from a JPA application?

I'm not the only one to have a problem with this issue. Have a look at this discussion:

http://stackoverflow.com/questions/21645516/program-using-hibernate-does-not-terminate

I think that the Hibernate team should have a look at this.

Marcos

This is serious. This is happening. It is a huge bug. You can test if for yourself and confirm. And yet no one seems to care.

Marcos

Same problem here.
http://stackoverflow.com/questions/21943526/hibernate-app-doesnt-close-after-crash

Hi Marcos,
good catch, thanks for the heads up!

I've created https://hibernate.atlassian.net/browse/HHH-8998
Feel free to report such issues on JIRA directly.

Hi cscleison,
sorry but no that's not a Hibernate bug, you're in charge of closing the resources you open. I've replied on stackoverlow as well to avoid confusing other people, please flag it as a correct answer, that would be helpful to others.

Hi Sanne,
Thank you for your feedback. I was in doubt whether it was really a bug or my fault.