On 2013-08-12 17:15, davide.cavestro wrote:
Follows a partial call stack for a /Connection.close()/ call. I took it at
JVM shutdown time for the Tomcat main thread on a JRockit JVM :
The DB size issue is probably down to fragmentation and fill-factor in
the internal data-structures.
I don't see that we'll be able to improve things much here.
The shutdown issue is more interesting.
It's spending time cleaning up the temporary LOB's that get created when
we need to pass them around, or when other things are casted into being
an LOB.
Is it possible that something in your code is either casting to an LOB
when it retrieves data, or passing data in or out of H2 using
InputStream or OutputStream?
e.g. calling getOutputStream() on a ResultSet.
It doesn't look like we clean those things anywhere except for during a
shutdown(), which is a potential problem if you manage to generate a lot
of them.
--
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/groups/opt_out.
