Hello to all,

we're caching all objects by an own-build java cache. One object contains a Blob, which is read by the application with the getBinaryStream()-method. After having started the application, everything runs fine.

However, after running a while (~1 hour or so), calling the getBinaryStream()-method leads to the following error:

Caused by: java.io.IOException: Must be logged on to server
at oracle.jdbc.driver.DatabaseError.SQLToIOException(DatabaseError.java:557)

I assume, that hibernate closed the connection to the database after a while. When taking the Blob out of the own-build cache, the connection might have already been closed by hibernate. How can I enforce hibernate to reopen the connection for the specific object?

Thanks in advance,

Volker

Well just looking at the subject line "Closed DB connection when calling Blob.getBinaryStream()" makes me think of trying to access the BLOB data stream in a succeeding transaction, ie:

hibSession = ...

tx = beginTransaction();
myBean = myDao.findById( id );
tx.commit();

tx = beginTransaction();
... myBean.getMyBlobMember().getBinaryStream();
tx.commit();

hibSession.close();

The above scenario would be typical when using a long session. Oracle LOB locators are normally only valid in the same transaction as they were loaded in, so getBinaryStream() above could only be called in the first transaction above. And yes, Oracle will complain about "closed connection" while it is really only the transaction that is gone.

//Mike