Try using something like Netbeans Profiler or Eclipse Memory Analyzer to see who is holding those objects in memory.
Martin wrote: > Hello, > I generate Strings in Java, which contains SQL statements like > INSERT INTO myTable VALUES (...),(...),(...),... ; > > > This happens in Thread1 of 2 Threads (but threads doesn't seem to be > the problem). > > Strings are sent to Thread2, where I call > statement.executeUpdate(myString); > > If I remove the last command I typed above, everything is ok.(simply > it doesn´t work with database) > But if I leave the command at it's place, program consumes more and > more memory every second. > > I profiled the program and I found out, that the most of memory is > consumpted by Strings, chars, bytes, Longs etc. Objects or types that > are used in sql INSERT statements. > > Is this standard behaviour of H2 DB? > Should I do something with cache(I tried without success) or with > something else? > > Thanks. > > Martin > -- 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.
