In my application I use the long conversations. After process a request, I store the disconnected session in HttpSession and on next request, reconnect the stored session and work with it further. In Hibernate3 is the reconnect() method deprecated, what must I use instead of this? This I saw in the API documentation: "Manual reconnection is only needed in the case of application-supplied connections, in which case the Session.reconnect(java.sql.Connection) for should be used. " I use no application-supplied connections, and I don't want use they, because I need no manually connection control, and I want to keep the abstraction to the underlying JDBC connection. Must I leave the connection active? But in this case I will possibly have too many opened database connections!
Can you give me an advice?

Thanks.

Take a look at the Field Summary section of http://www.hibernate.org/hib_docs/v3/api/org/hibernate/ConnectionReleaseMode.html

In Hibernate 3.1 or later, by default JDBC connections are automatically released at the end of a transaction (it's using the AFTER_TRANSACTION option from the link above) and reconncected as necessary. So the only reason you would ever need to explicitly reconnect in the session is if you're using application-supplied connections (i.e. you're *not* using a connection pool). And in that case you have to provide the Connection object using reconnect(Connection), so the no-argument reconnect() is unnecessary.

This is good news. It means you don't have to store any connections in your session or do anything special with the connections. The default in Hibernate 3.1 or later is to aggressively release the connection at the end of a transaction and reconnect for you automatically as necessary.