Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Check if you're not creating unused SQL entities, as it might cause this exception.

Solutions on the web

via dzone.com by Unknown author, 1 year ago
The object is already closed [90007-172]
via GitHub by marcellodesales
, 2 years ago
Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-176]
via Stack Overflow by gabriel angelos
, 2 years ago
Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-169]
via GitHub by marcellodesales
, 2 years ago
Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-176]
via GitHub by mingliu
, 2 years ago
Database may be already in use: "Locked by another computer: 172.17.0.2". Possible solutions: close all other connection(s); use the server mode [9 0020-176]
via Stack Overflow by bubesh
, 2 years ago
Deadlock detected. The current transaction was rolled back. Details: " Session #64 (user: SA) is waiting to lock PUBLIC.QRTZ_SIMPLE_TRIGGERS while locking PUBLIC.QRTZ_TRIGGERS (exclusive). Session #67 (user: SA) is waiting to lock
org.h2.jdbc.JdbcSQLException: The object is already closed [90007-172]	at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)	at org.h2.message.DbException.get(DbException.java:169)	at org.h2.message.DbException.get(DbException.java:146)