>
>
> As I noted, its 'locks' list had been empty before the moment when
> 'this.rollback();' was invoked in 'Session#close'. As a result,
> 'Session#unlockAll' does not release exclusive lock on the meta table.
> Probably, this lock should be released in some other way?
>
>
Hmm, what is weird is that according to your debugging output, session #18
has the problematic lock in it's locks list:
ockExclusiveSession = {org.h2.engine.Session@12711} "#18 (user: SA)"
serialId = 18
database = {org.h2.engine.Database@12701}
"TEST2:org.h2.engine.Database@5726a512"
connectionInfo = null
user = {org.h2.engine.User@12839} "SA:2:org.h2.engine.User@5b910dbc"
id = 8
locks = {java.util.ArrayList@13427} size = 1
0 = {org.h2.mvstore.db.MVTable@12700} "PUBLIC.SYS"
which means that somehow session #18 was closed in such a way that it did
not manage to free this lock.
Are you sure there were no previous exceptions logged which indicate why it
closed this way?
--
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 https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
