db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald McLean <dmclea...@gmail.com>
Subject Re: 'ERROR 40XD0: Container has been closed.: java.io.IOException'.
Date Mon, 15 Feb 2010 13:15:50 GMT
When working with BLOBs and CLOBs, these sorts of errors are almost always
caused by committed transactions. Since most people don't expect to need a
 for a select, more often than not autocommit is set to TRUE and the select
commits as soon as it is executed. While this is fine for everything else,
it doesn't work for BLOB/CLOB fields. A BLOB/CLOB is only valid inside a
single transaction and the instant that transaction finished (commit or
rollback) the BLOB/CLOB goes poof.


On Mon, Feb 15, 2010 at 2:33 AM, Dinesh Bajaj <dinesh.bajaj@ymail.com>wrote:

> I get the above error while executing the Update statement through a java
> application. The error occurs when the update statement involves a Blob
> field.
> I have ensured that input stream being given to setBinaryStream method is
> not closed and the length being given is also correct.
> Also, may I say that I can't find any source where I can readily find the
> detailed description of a Derby error and its possible causes. The reference
> documentation just cryptically says : "Container has been closed". Now, what
> can be make out of this?
Family photographs are a critical legacy for
ourselves and our descendants. Protect that
legacy with a digital backup and recovery plan.

Join the photo preservation advocacy Facebook group:

View raw message