Nice work.
I think you have something wrong with your query, because it's trying to return a seriously large number of records.

On 2012-11-05 13:54, kais haddadin wrote:
Ok I did what you recommended. The dump file was 16GB so it took a while to open it. I am not sure what information should I provide here: The Thread stack for the exception is as follows:

main
   at java.lang.OutOfMemoryError.<init>()V (Unknown Source)
   at org.h2.expression.Aggregate.updateAggregate(Lorg/h2/engine/Session;)V 
(Aggregate.java:242)
   at org.h2.expression.Alias.updateAggregate(Lorg/h2/engine/Session;)V 
(Alias.java:76)
   at org.h2.command.dml.Select.queryGroup(ILorg/h2/result/LocalResult;)V 
(Select.java:339)
   at 
org.h2.command.dml.Select.queryWithoutCache(ILorg/h2/result/ResultTarget;)Lorg/h2/result/LocalResult;
 (Select.java:613)
   at 
org.h2.command.dml.Query.query(ILorg/h2/result/ResultTarget;)Lorg/h2/result/LocalResult;
 (Query.java:307)
   at org.h2.command.dml.Query.query(I)Lorg/h2/result/LocalResult; 
(Query.java:277)
   at org.h2.command.dml.Query.query(I)Lorg/h2/result/ResultInterface; 
(Query.java:36)
   at org.h2.command.CommandContainer.query(I)Lorg/h2/result/ResultInterface; 
(CommandContainer.java:86)
   at org.h2.command.Command.executeQuery(IZ)Lorg/h2/result/ResultInterface; 
(Command.java:191)
   at org.h2.jdbc.JdbcStatement.executeInternal(Ljava/lang/String;)Z 
(JdbcStatement.java:173)
   at org.h2.jdbc.JdbcStatement.execute(Ljava/lang/String;)Z 
(JdbcStatement.java:152)
   at org.h2.tools.Shell.execute(Ljava/lang/String;)V (Shell.java:429)
   at org.h2.tools.Shell.promptLoop()V (Shell.java:270)
   at org.h2.tools.Shell.runTool([Ljava/lang/String;)V (Shell.java:148)
   at org.h2.tools.Shell.main([Ljava/lang/String;)V (Shell.java:80)

I attached 2 snapshots of the histogram and the dominator_tree.


Am Montag, 5. November 2012 11:20:24 UTC+1 schrieb Noel Grandin:


    On 2012-11-05 12:15, Kais Haddadin wrote:
    > when assigning 12GB as Xmx, the JVM went to 9.1G, and then the
    out of
    > memory.
    > when assigning 15GB on the 16GB machine, the JVM went to 10.6GB and
    > then the exception came. I am not sure how many GB does such a
    query
    > need in H2? Is there a possibility to enhance such queries to use
    >
    > Cheers,
    > Kais
    >

    You could try debugging it with -XX:+HeapDumpOnOutOfMemoryError and
    Eclipse Memory Analyzer.

--
You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/dHoUqfZNlcsJ.
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