I'm using Hibernate 3.3.2. I've got a working Hibernate application that successfully reads from an Oracle database.

What I'm not sure about is that at night, the database is turned off whilst backups go on. This aint a problem - I can easily say at a certain time, use a different configuration and "point" my application to another database.
But this, I think, will leave the original connections floating around. Is Hibernate/c3po clever enough to re-establish and then re-use connections when the original database comes back again, or will it re connection with a new set of connections - leaving the original sewt behind ? (thinking of memory leaks and such like...)

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:


Problems with Session and transaction handling?

Read this: http://hibernate.org/42.html