This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-01
Channels
- # announcements (21)
- # architecture (6)
- # aws (18)
- # babashka (14)
- # beginners (231)
- # boot (1)
- # calva (2)
- # chlorine-clover (22)
- # cider (34)
- # clara (16)
- # clj-kondo (53)
- # cljdoc (5)
- # cljs-dev (22)
- # cljsrn (3)
- # clojure (283)
- # clojure-europe (24)
- # clojure-italy (9)
- # clojure-nl (5)
- # clojure-spec (5)
- # clojure-uk (57)
- # clojurescript (14)
- # core-typed (8)
- # cursive (4)
- # data-science (11)
- # datomic (41)
- # docker (24)
- # duct (2)
- # emacs (2)
- # exercism (29)
- # fulcro (96)
- # graalvm (4)
- # jobs-discuss (1)
- # kaocha (53)
- # lambdaisland (20)
- # malli (5)
- # nrepl (4)
- # observability (7)
- # off-topic (40)
- # pathom (44)
- # pedestal (8)
- # re-frame (19)
- # shadow-cljs (58)
- # spacemacs (2)
- # sql (9)
- # tools-deps (15)
- # vim (3)
- # yada (10)
I'm attempting to deploy an uberjar to elastic beanstalk for the first time. I'm using the preconfigured Java platform. I have a main class compiled in my jar and working properly on my local machine, ie I can just do
java -jar MyProject.jar
And it starts up properly (locally).
I have uploaded this jar to my beanstalk app. But when I visit the URL I just get a 502 Bad Gateway.
the web.log is showing
-------------------------------------
/var/log/web-1.log
-------------------------------------
Clojure 1.6.0
user=>
I'm not seeing clojure 1.6 at all in my deps tree.
Any tips on how I can start to debug this? Is there anything else I need to do to prepare the jar?it looks like your jar is specifying clojure.main as the Main-Class, which just starts the clojure repl
so however you are building your jar isn't setting the Main-Class attribute to whatever your main class is
My manifest.mf in the jar looks like this
Manifest-Version: 1.0
Built-By: depstar
Build-Jdk: 13.0.1
Multi-Release: true
Main-Class: main
where the main
namespace is indeed the correct main class (yeah I know horrible name and single segment namespaces are not a good practice... that shouldn't be the issue though right?)I think I might have to do additional config related stuff for beanstalk instead of just using the regular jar
I would double check that the beanstalk jar is the same one you are looking at locally, because that looks like a jar launched with a main class of clojure.main
it would say clojure.main then
or look back over whatever tutorial you are looking at (I assume you are working from some tutorial because you are using clojure 1.6.0)
that's the thing though I'm not using clojure 1.6, and it doesn't appear in my deps tree via clj -Stree