Hi,

As you can see below this very simple program causes a stack overflow. If I comment out the .connection() and reconnect() lines there is no problem. This code used to work in 3.1.

Any help would be greatly appreciated.

Thanks,
Yair

Hibernate version: 3.1.3

Mapping documents: test with error doesn't have any mapping

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

Connection conn = session.connection();
session.reconnect(conn);


Full stack trace of any exception that occurs:

java.lang.StackOverflowError
at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:54)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:40)
at $Proxy0.isClosed(Unknown Source)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:40)
at $Proxy0.isClosed(Unknown Source)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:40)
at $Proxy0.isClosed(Unknown Source)
...

Name and version of the database you are using:
Oracle 10g

The generated SQL (show_sql=true):

No SQL is generated

Can you reconnect a session that hasn't been disconnected? Try this, instead:

Well the code itself works, but it is not what I am after. I want to "take" the connection from the session and then reconnect it and keep working with the session. I use this in my code to run a "set transaction read only" statement on the connection, thus making the session see a read only view of the database. Another use is to insert rows into the database not through Hibernate, but using the session object's connection.

Thanks,
Yair

Why do you need to reconnect in that situation? Can't you just use the connection returned from connection()?

Well, if I don't reconnect, then the connection will not be closed when I use session.close() and will leak. Is this not the case?

Thanks

That's not the case.

If you're using Hibernate-supplied connections, it's your responsibility to close the connection (after you're done with it and after you close the hibernate session). At no point are you supposed to reconnect the connection.

So what you are saying is that if the connection comes from Hibernate (e.g. using c3p0 as the backend connection pool), and I use the session.connection() call, the only way that this connection is returned to the pool is if I call connection.close() myself?

Also, if I use the connection() call, and subsequently continue to use the session object, will it continue to use the same connection or acquire a new one? I would like it to use the same connection, so that I can call "set transaction read only" on it and then use Hibernate for the rest of my DB access.

Thanks

1) Only if you're using aggressive connection release, but I believe that c3p0 does. You should verify this.

2) Yes, hibernate will continue to use the same connection, so don't close the connection until after you close the session.