komga: SQL Error: 90098, SQLState: 90098 The database has been closed

Trying to run Komga inside Docker and it all seems to work fine, but after a few minutes of using up 100% of the CPU and ~4.5GB of RAM, it starts showing

WARN 1 --- [kTaskExecutor-1] o.h.engine.jdbc.spi.SqlExceptionHelper   : SQL Error: 90098, SQLState: 90098,
ERROR 1 --- [kTaskExecutor-1] o.h.engine.jdbc.spi.SqlExceptionHelper   : The database has been closed [90098-200],
INFO 1 --- [kTaskExecutor-1] o.h.e.internal.DefaultLoadEventListener  : HHH000327: Error performing load command : org.hibernate.exception.JDBCConnectionException: could not extract ResultSet

in the logs, and all I get is 504 timeouts from that point on. It’s still using up a lot of CPU, but the logs have a lot of exceptions about the database being closed.

I have around 600GB of PDFs and CBZ/CBRs.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 23 (8 by maintainers)

Most upvoted comments

I found out why this was the case. I had a 3.0GB PDF 😄 with an equivalent 65MB cbz file. I guess the PDF was 156 high-quality pages. Removing the huge PDF fixed it! Web UI is stable now (or seems to be).

@gotson I confirm that on the latest Docker image, JPEG2000 PDFs now work.