I updated h2 and there were A LOT of changes.
When I built it, it turned out that the jar was 1.3.147 instead of 1.2.147 as before.
So I suppose you changed the head of trunk from 1.2 to 1.3?

And indeed the errors I reported have disappeared with the newest version.
I get them everytime I use the older 1.2.147 but never with 1.3.147.

So even though you could not reproduce the problem you somehow managed to fix it! ;-)
Thank you.

- Rami

6.12.2010 8:46, Thomas Mueller kirjoitti:
Hi,

I'm sorry, I can't reproduce the problem using your database. Could
you try again using the newest version, and then post the complete
stack trace? I think you didn't post the complete one (but I'm not
sure).

Regards,
Thomas


On Sat, Nov 27, 2010 at 7:25 PM, Rami<[email protected]>  wrote:
I created a new database that contains a single IMAGE table in PUBLIC
schema.

CREATE TABLE PUBLIC.IMAGE (
     IMAGE_ID IDENTITY PRIMARY KEY,
     BYTES BLOB
);

Example URL
jdbc:h2:tcp://localhost:10000/TEST;user=test;password=user

You can download the database from Rapidshare
http://rapidshare.com/files/433495007/TestDb.tar.gz
(The size is 274MB so hopefully you are a RapidPro user :)

It contains 3157 images and the size of them all is 286 274 562 bytes =
273MB
I ran your test case against this table (obviously the server startup and
table creation / population has to be removed)

And I get exceptions like

java.lang.NegativeArraySizeException

         at
org.h2.util.Utils.newBytes(Utils.java:355)

         at
org.h2.store.Data.expand(Data.java:1079)&n
bsp;
         at
org.h2.store.Data.checkCapacity(Data.java:1074)&
nbsp;
         at
org.h2.store.FileStoreInputStream.fillBuffer(FileStoreInputStream.java:100)
         at
org.h2.store.FileStoreInputStream.readBlock(FileStoreInputStream.java:73)
         at
org.h2.store.FileStoreInputStream.read(FileStoreInputStream.java:61)&nbs
p;
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

Exception in thread "Thread-6" java.lang.OutOfMemoryError: Requested memory:
987040432
         at org.h2.util.Utils.newBytes(Utils.java:357)
         at org.h2.store.Data.expand(Data.java:1079)
         at org.h2.store.Data.checkCapacity(Data.java:1074)
         at
org.h2.store.FileStoreInputStream.fillBuffer(FileStoreInputStream.java:100)
         at
org.h2.store.FileStoreInputStream.readBlock(FileStoreInputStream.java:73)
         at
org.h2.store.FileStoreInputStream.read(FileStoreInputStream.java:61)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

Here one can only wonder why would H2 request 941 megs of memory.

Hope this helps.

- Rami

Thomas Mueller wrote:
Hi,

For multiple reasons, your test case is not reproducible:

- the create table statements are missing - the data is missing
(insert statements) - the test is not self-contained - I can't
reproduce the problem

My test case is:
http://h2database.com/p.html#7051c1db4cfd824bb7c45e29c4d15ac6

Regards, Thomas

--
You received this message because you are subscribed to the Google Groups
"H2 Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.


--
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en.

Reply via email to