Hi,
I'm currently experimenting performance issues with the aggregate operation.
Here is my data : A historic of values for different ids
CREATE TABLE Bench (id INT NOT NULL, value INT NOT NULL, T TIMESTAMP NOT
NULL)
Thereafter I insert a lot of data in it (generated). My parameter for
generatio
Thanks for the reply. I tried that as shown below and I still get the
stack track.
jdbc:h2:tcp://localhost/mem:test-db;create=true;DB_CLOSE_ON_EXIT=FALSE
I don't know if I mentioned before that I'm using EclipseLink. I'm not
sure if that is relevant or not.
Here is the full stack trace in case i
My best guess would be one of two things
(1) something is closing the connection obtained from
DbStarter#getConnection, which is a no-no
or
(2) Jetty is calling DbStarter#contextDestroyed more than once, which
isn't great, but we should ideally be tolerant of that.
Can you turn on the trace a
This is the results when I start the web application, run some unit
tests, clear the terminal and then do a "mvn jetty:stop"
Is that what you wanted to see?
Killing Jetty
02-14 08:29:37 database: closing mem:test-db from shutdown hook
02-14 08:29:37 database: disconnecting session #2
02-14 08:29:
Yes.
That means that the DB_CLOSE_ON_EXIT=FALSE flag is not working. Are you
sure you tested with that flag in place?
On 2012-02-14 16:31, zaraki kenpachi wrote:
from shutdown hook
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to
