Hello, Thomas.
I prepare some test case for you in coming days.
Vitali.
On Wednesday, September 17, 2014 9:54:21 AM UTC+3, Thomas Mueller wrote:
>
> Hi,
>
> I will try to improve the error message / stack trace, but maybe the
> "object is already closed" is unrelated to the other problem ("Chunk ...
> not found").
>
> If you have a reproducible test case, that would be great. Or a database
> you can send me, so I can reproduce it.
>
> Regards,
> Thomas
>
>
> On Tuesday, September 16, 2014, Vitali <[email protected] <javascript:>>
> wrote:
>
>> Usually everything starts with
>> Caused by: org.h2.jdbc.JdbcSQLException: The object is already closed;
>> SQL statement:
>>
>> exception on INSERT or UPDATE query where BLOB type is taking part.
>>
>> UPDATE "X"."A" SET "TYYPPI" = ?,"ITEMID" = ?,"SHAPE" = ? WHERE ("A_ID" =
>> ?) [90007-181]
>> at
>> org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
>> at org.h2.message.DbException.get(DbException.java:179)
>> at org.h2.message.DbException.get(DbException.java:155)
>> at org.h2.message.DbException.get(DbException.java:144)
>> at org.h2.store.LobStorageMap.createBlob(LobStorageMap.java:128)
>> at org.h2.value.ValueLobDb.link(ValueLobDb.java:254)
>> at org.h2.mvstore.db.MVPrimaryIndex.add(MVPrimaryIndex.java:120)
>> at org.h2.mvstore.db.MVTable.addRow(MVTable.java:620)
>> at org.h2.table.Table.updateRows(Table.java:466)
>> at org.h2.command.dml.Update.update(Update.java:145)
>> at org.h2.command.CommandContainer.update(CommandContainer.java:78)
>> at org.h2.command.Command.executeUpdate(Command.java:254)
>> at
>> org.h2.jdbc.JdbcPreparedStatement.execute(JdbcPreparedStatement.java:198)
>> at
>> org.apache.commons.dbcp2.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:198)
>> at
>> org.apache.commons.dbcp2.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:198)
>> at org.geotools.jdbc.JDBCDataStore.update(JDBCDataStore.java:1570)
>>
>>
>> looks like something happens with BLOB's InputStream that is closed
>> before it should be used..
>>
>> Currently with high probability of exceptions I get this problem in
>> INSERT...SELECT.. queries where BLOBs are as well.
>>
>> Vitali.
>>
>> On Monday, September 15, 2014 10:55:41 AM UTC+3, Thomas Mueller wrote:
>>>
>>> Hi,
>>>
>>> Could you provide a reproducible test case? If not, I would need to have
>>> a more detailed description on the operations that were run.
>>>
>>> Regards,
>>> Thomas
>>>
>>>
>>>
>>> On Mon, Sep 15, 2014 at 9:38 AM, Vitali Diatchkov <[email protected]>
>>> wrote:
>>>
>>>>
>>>> I am observing similar issue with lost chunks. See my post about
>>>> BLOBs at 13.09.2014. Randomly in multi-threaded environment and MVStore
>>>> enabled the database becomes corrupted.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "H2 Database" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at http://groups.google.com/group/h2-database.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "H2 Database" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/h2-database.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
