Fork me on GitHub
#aws
<
2019-05-06
>
mss20:05:49

using cognitect’s aws api for the first time, and getting an error: Exception in thread "async-dispatch-1" java.lang.NoClassDefFoundError: org/eclipse/jetty/util/thread/NonBlockingThread when attempting to invoke (def s3 (aws/client {:api :s3})) per the example in the readme. if anyone has any ideas what could be causing that, I’m all ears

alexmiller20:05:23

what are your deps?

mss20:05:36

using a lein project.clj, which I assume is the root of the issue

mss20:05:54

first time using a lib that declares its deps using deps.edn afaik, so if I’m missing something about how those might fit together that’s likely it

ghadi20:05:36

@mss lein is fine, paste your deps --- you'll need three

mss20:05:01

[com.cognitect.aws/api "0.8.301"]
[com.cognitect.aws/endpoints "1.1.11.537"]
[com.cognitect.aws/s3 "714.2.430.0"]

ghadi20:05:07

that seems correct

mss20:05:26

yeah no weird exclusions that I can tell either

ghadi20:05:38

can you paste the output of lein deps :tree

mss20:05:58

get the same error regardless of whether I add the ring/jetty-io exclusion or not

ghadi20:05:38

are you sure?

mss20:05:56

lemme sanity check it just to be sure. gimme a sec

ghadi20:05:57

it looks like ring-jetty-adapter is forcing an older version of jetty (9.2)

mss20:05:59

thank you for the help btw!

ghadi20:05:11

aws-api needs jetty 9.3 IIRC

mss20:05:49

fwiw, if I bump my ring version to 1.7.1 (latest IIRC) and it defaults to using the cognitect jetty-io version, I get a different error about thread pool exhaustion

mss20:05:49

lemme run through the with/without exclusion on ring 1.6.3 and I can get you the error message on ring 1.7.1

ghadi20:05:04

jetty should be at "9.3.7.v20160115" when you'll have everything working correctly

mss20:05:58

yep, just went ahead and added that specific version to my deps and all is well

mss20:05:01

thanks for the help troubleshooting

ghadi20:05:17

my pleasure