> Is the problem possibly a difference between your
> compilation environment and your deploy env?
This seems to be proven by the fact that upgrading Java on the EC2 instance
fixed the problem.
On Wednesday, January 16, 2019 at 3:49:41 PM UTC-5, Chris Nuernberger wrote:
>
> Are you using
Are you using aot?
We have used that durable queue with 1.8. In fact, we have a compatibility
later that allows you to move from the durable queue to an Aws queue:
(mostly undocumented)
https://github.com/techascent/tech.queue
Is the problem possibly a difference between your compilation
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?
On Wednesday, January 16, 2019 at 3:17:49 PM UTC-5, lawrence...@gmail.com
wrote:
>
>
On the new EC2 instance, running Ubuntu:
java -version
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-0ubuntu0.18.04.1-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
Is it possible this version does not have the checksum signature that
Sorry, I'm an idiot. The real error was when I called put!
I don't understand this error:
INFO: java.lang.NoSuchMethodError: java.util.zip.Checksum.update([B)V
java.lang.NoSuchMethodError: java.util.zip.Checksum.update([B)V
at durable_queue$checksum.invokeStatic (durable_queue.clj:64)
I was away from Clojure for a year and I missed it. I am pleased to be
back. But I've forgotten certain common errors. I feel like this is
something I used to know but now I've lost the knowledge.
I'm using Factual's durable-queue to put a step inbetween the import of
large JSON files, and
