Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Java Hibernate Basics Persisting Data with Hibernate Saving Data with Hibernate

Adam Warzel
Adam Warzel
650 Points

Shouldn't sessionFactory.close() ?

Shouldn't sessionFactory.close() be called in the end of the program? Otherwise the application hangs.

1 Answer

In general, your application should have one sessionFactory which you open when you needed and close it when your are with it .... example ... when you exist a DAL method. I am not familiar with the video you are referring to, but if the video app is closing closing a running app and exiting the program ... then the memory will be freed anyway. It a good practice close the sessionFactory, before existing, regardless.