I'm currently on Metabase 0.52.6. Checked for a new download and got 0.53.1. Backed up the original and dropped the new version in place. Tried starting it and I get a bunch of errors, starting with:
E:\Program Files\Metabase>java -jar metabase.jar
Exception in thread "main" java.lang.NoClassDefFoundError: java/util/SequencedCollection
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:467)
at clojure.lang.RT.classForName(RT.java:2229)
at clojure.lang.RT.classForName(RT.java:2238)
at instaparse.auto_flatten_seq$fn__6961.(auto_flatten_seq.clj:314)
at instaparse.auto_flatten_seq__init.load(Unknown Source)
at instaparse.auto_flatten_seq__init.(Unknown Source)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:467)
at clojure.lang.RT.classForName(RT.java:2229)
at clojure.lang.RT.classForName(RT.java:2238)
at clojure.lang.RT.loadClassForName(RT.java:2257)
at clojure.lang.RT.load(RT.java:469)
at clojure.lang.RT.load(RT.java:444)
at clojure.core$load$fn__6931.invoke(core.clj:6189)
Fortunately I can revert back to 0.52.6. Meanwhile, any idea as to why this is being problematic? I do use the open source version, and downloaded it again, on the off chance that I'd gotten the commercial version instead. Same error. Microsoft java OpenJDK version 17.0.2 in a Windows 2019 server environment in an Azure VM. 16 Gb RAM, with 4 Gb being listed as being available to Java. Do I need an intermediate version between 0.52.6 and 0.53.1 to apply first? If so, where do I get it?
I got an error while trying to upgrade from version 0.52.9 to version 0.53.1.
I saw the comment here and checked the java version. The java version is 11.
I first changed the java version to 21 using the command below.
Then when I upgraded the metabase, the problem was solved.
If anyone has a similar problem, this information may help.
Thanks for the java upgrade suggestion. Will try that next. It would be useful on the upgrade page to list the java version required, possibly with a link to relevant pages. Would save a bit of time and frustration knowing this beforehand.
Perhaps in the beginning of the code, have it check the the version of Java installed against what it needs. If it matches, continue, otherwise output a message like "Metabase needs version xx of java to run. Please upgrade and try again." rather than crashing with java errors that don't explain the issue.
Quite simply, just add a warning on the update page in the admin area if the upcoming update might have compatibility issues with the current Java environment, just like the warning you added for the old Slack bot. You plan new system requirements in advance anyway. I ran into the same problem. I subscribed to your newsletter but it seems i missed it.