db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: 'ERROR 40XD0: Container has been closed.: java.io.IOException'.
Date Mon, 15 Feb 2010 14:11:10 GMT
On 15.02.10 14:15, Donald McLean wrote:
> 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
> transaction
>   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.


What Donald says is very true, but we have had some bugs in this area.
If following Donald's advice doesn't help you, please post the relevant 
part of your code (preferably in a runnable state) and the full stack trace.


> Donald
> 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?

View raw message