Version 0.23 not working on Java 1.7 #4586
Assignees
Labels
Operation/
Priority:P1
Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness
Type:Bug
Product defects
Milestone
Comments
|
what's the rest of that stack trace? anything show up after? |
|
What's your Java version? |
|
Updating to the newest java version fixed it for me. |
|
@LukeAbell what version were you using beforehand? |
|
I am having the same issue. This is the java version [ec2-user@ip-172-31-22-25 ~]$ java -version
java version "1.7.0_131"
OpenJDK Runtime Environment (amzn-2.6.9.0.71.amzn1-x86_64 u131-b00)
OpenJDK 64-Bit Server VM (build 24.131-b00, mixed mode) |
|
And solved by upgrading to java 1.8 [ec2-user@ip-172-31-22-25 ~]$ java -version
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) |
|
Hi, I was running version 1.7 I upgrade to version 1.8 Now it's working. |
|
another example -- http://discourse.metabase.com/t/cant-run-latest-version/1289 |
salsakran
changed the title
salsakran
added
Priority:P1
|
I was able to obtain a full stacktrace for this Looks like the issue here is that the embedding library we're using is making use of the new Not 100% sure why it still works if you run via Leiningen (as the tests do) but not when you run via the JAR. It's possible that the lib is doing a runtime check and using the |
|
There's probably some way to tweak the behavior, we've ran into a similar issue in the past |
|
(For the manifold library, we had add the JVM option to the compilation profile) |
|
Yup my suspicions are confirmed (from the source) (defmacro ^:private apply-jdk8-extensions
[]
(try
(Class/forName "java.time.Instant")
`(extend-protocol ITimestamp
java.time.Instant
(to-timestamp [obj#]
(.getEpochSecond ^java.time.Instant obj#)))
(catch ClassNotFoundException e
;; pass
)))
(apply-jdk8-extensions)unfortunately the macros get |
|
Opened an issue here: funcool/buddy-sign#41 I'm 90% of the way to a fix so hoping I can open a PR for the lib and we get a new release so we can push the fix. Otherwise in the meantime we will have to make sure we compile the uberjar with Java 7 |
|
Opened a PR to fix this issue at funcool/buddy-sign#42. Hoping we can get it merged soon so all we need to do to resolve this issue is bump our dependency. In the meantime, building the uberjar with Java 7 should fix the issue. |
|
I've confirmed building the uberjar with Java 7 resolves the issue as well |
|
hmm. sounds like a reason to start doing our builds in docker containers. |
|
@camsaul thanks! the fix make sense! Tomorrow at first time (9-10 am CEST aprox) I will merge it and release a new version! |
|
Awesome @niwinz, thanks! 🎉 |
|
Fixed by #4652 |
|
Recently, I have faced same error when I lunched pycharm. I have upgrade Java from With the help of following command. My system specifications:
|
|
where in the documentation does it describe that the variables "MB_DB_...." should be set? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I always runned metabase from the jar file. Like always i stopped metabase, replace the .jar for the new 0.23 .jar file but when i try to start i get this error.
My sh contains this:
Thanks for being part of the Metabase project!
The text was updated successfully, but these errors were encountered: