Logs get filled with "ERROR async.streaming-response :: Error determining whether HTTP request was canceled java.lang.ClassCastException" generating a high CPU load on the server

Hello,

we migrated from Metabase 0.34.0 to 0.42.2 a couple of months ago and since then we are facing this issue:
the logs get filled with "ERROR async.streaming-response :: Error determining whether HTTP request was canceled java.lang.ClassCastException" errors, every second, which makes the CPU load go really high.
The only mitigation to that is to restart the docker container.
We are self-hosting Metabase with Jetty & SSL, on docker, with a PostgreSQL DB.

I found some similar issues on the board, but nothing conclusive.

Thank you,

{
  "browser-info": {
    "language": "fr-FR",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.14.1+1",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "11.0.14.1",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.14.1+1",
    "os.name": "Linux",
    "os.version": "3.10.0-1160.53.1.el7.x86_64",
    "user.language": "en",
    "user.timezone": "GMT"
  },
  "metabase-info": {
    "databases": [
      "postgres"
    ],
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "9.6.18"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.2.23"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2022-02-28",
      "tag": "v0.42.2",
      "branch": "release-x.42.x",
      "hash": "d6ff494"
    },
    "settings": {
      "report-timezone": null
    }
  }
}

Hi @thomasr
This error can be generated when using SSL in Jetty. Use a reverse-proxy to handle SSL.
ERROR async.streaming-response when Jetty SSL enabled · Issue #13771 · metabase/metabase · GitHub - upvote by clicking :+1: on the first post
Latest release is 0.44.1

Hi @flamber,

thank you, I'll look into it!