Query fails with: Interrupt task is already scheduled for the thread

Recently, I am facing issues with dashboards and questions that fail with the following SQLException:

An SQLException was provoked by the following failure: java.lang.IllegalStateException: Interrupt task is already scheduled for the thread Thread[#102,streaming-response-thread-pool-2,5,main] and the type SO_TIMEOUT

This started happening after I updated from 0.57.4.2 to 0.58.7.4 or v0.58.8, but I'm not sure if this is the root cause or if it could be due to Metabase/DB being overloaded ? After restarting the Metabase service, it works normally for about two days, then starts to fail.

Related questions do query in the Oracle database. I also updated the ojdbc8.jar file, but there was no improvement. What could be the reason?

{
  "browser-info": {
    "language": "cs-CZ",
    "platform": "Win32",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "metabase-info": {
    "databases": [
      "oracle",
      "h2",
      "mysql",
      "sqlserver"
    ],
    "run-mode": "prod",
    "plan-alias": "",
    "version": {
      "date": "2026-02-27",
      "tag": "v0.58.8",
      "hash": "c2b1490"
    },
    "settings": {
      "report-timezone": null
    },
    "hosting-env": "unknown",
    "application-database": "mysql",
    "application-database-details": {
      "database": {
        "name": "MariaDB",
        "version": "10.11.15-MariaDB"
      },
      "jdbc-driver": {
        "name": "MariaDB Connector/J",
        "version": "2.7.10"
      }
    }
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "21.0.6+7-LTS",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "21.0.6",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "21.0.6+7-LTS",
    "os.name": "Windows Server 2019",
    "os.version": "10.0",
    "user.language": "en",
    "user.timezone": "Europe/Paris"
  }
}

This is a known issue in certain versions of the Oracle JDBC driver. Try upgrading to a version released with Database 21 or later.

Additional information:

Hi, updating the Oracle JDBC driver helped. The Metabase documentation is a bit misleading in this aspect. It mentions that you need to use the ojdbc8.jar file and that the minimum version should be 19c. And since the connected database uses version 19c, I initially followed those instructions. Now I’m using the ojdbc8.jar file released with Database 21.

BTW, the old driver file should be deleted from the plugins folder. Renaming it seems like a bad idea, since the metabase may still load it.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.