aws

http://status.aws.amazon.com/ https://www.expeditedssl.com/aws-in-plain-english
2019-05-06T20:17:49.022100Z

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

alexmiller 2019-05-06T20:19:23.022600Z

what are your deps?

2019-05-06T20:20:36.022900Z

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

2019-05-06T20:20:54.023400Z

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

ghadi 2019-05-06T20:21:36.024100Z

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

2019-05-06T20:22:01.024500Z

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

ghadi 2019-05-06T20:23:07.024700Z

that seems correct

2019-05-06T20:23:26.025200Z

yeah no weird exclusions that I can tell either

ghadi 2019-05-06T20:24:38.025500Z

can you paste the output of lein deps :tree

2019-05-06T20:28:31.025700Z

2019-05-06T20:28:58.026400Z

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

ghadi 2019-05-06T20:30:38.026700Z

are you sure?

2019-05-06T20:30:56.027500Z

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

ghadi 2019-05-06T20:30:57.027700Z

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

2019-05-06T20:30:59.027800Z

thank you for the help btw!

ghadi 2019-05-06T20:31:02.028100Z

n.p.

ghadi 2019-05-06T20:31:11.028500Z

aws-api needs jetty 9.3 IIRC

2019-05-06T20:31:49.029300Z

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

2019-05-06T20:32:49.029900Z

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

ghadi 2019-05-06T20:33:04.030300Z

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

2019-05-06T20:34:58.030700Z

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

2019-05-06T20:35:01.030900Z

thanks for the help troubleshooting

ghadi 2019-05-06T20:35:17.031200Z

my pleasure