Open lkrubner opened 5 years ago
So, I upgraded to Java 11, and now everything works. So I guess this was a version conflict.
Just curious, but is there a way for Factual to make durable-queue to tell Leiningen that Java 11 is necessary?
I wouldn’t think Java 11 is required, since the library hasn’t changed since it was targeting Java 6. This sounds like a stray compilation artifact, and would likely be fixed by “lein clean”. On Wed, Jan 16, 2019 at 12:29 PM Lawrence Krubner notifications@github.com wrote:
So, I upgraded to Java 11, and now everything works. So I guess this was a version conflict.
Just curious, but is there a way for Factual to make durable-queue to tell Leiningen that Java 11 is necessary?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Factual/durable-queue/issues/22#issuecomment-454928668, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB6P1g5P0RmZrwH4YlpRSl4FSaISr5tks5vD4u-gaJpZM4aD3MS .
Just to be clear, the code worked fine on my MacBook Pro. But if I ran lein uberjar
and uploaded the uberjar to the EC2 instance, then I got the error on the EC2 instance. I don't see how that can be a stray compilation artifact. The problem was fixed when I upgraded the version of Java on the EC2 instance.
Okay, that sounds like a version mismatch between your dev environment and prod. If you compiled it on prod, it’d probably work without any upgrade. On Sat, Jan 19, 2019 at 8:34 AM Lawrence Krubner notifications@github.com wrote:
Just to be clear, the code worked fine on my MacBook Pro. But if I ran lein uberjar and uploaded the uberjar to the EC2 instance, then I got the error on the EC2 instance. I don't see how that can be a stray compilation artifact. The problem was fixed when I upgraded the version of Java on the EC2 instance.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Factual/durable-queue/issues/22#issuecomment-455794763, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB6P7k7wChSoO_CrH2Thmg0kGjrwcK4ks5vE0kTgaJpZM4aD3MS .
I think that at this point it's safe to close this issue as "not a bug"
I assume this is a version conflict, either of Java or Clojure or durable-queue. My code works fine on my local Macbook Pro, but I created a new EC2 instance with Ubuntu 18.04 and then I added Java:
On the EC2 instance I get this error on put!
Is this a matter of upgrading Java, or is this a matter of doing a data conversion before calling
put!
?I'm puzzled why this works on my Mac but not the EC2 instance.