This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-27
Channels
- # arachne (1)
- # beginners (31)
- # boot (84)
- # cider (9)
- # clara (2)
- # cljs-dev (102)
- # cljsrn (20)
- # clojure (254)
- # clojure-belgium (1)
- # clojure-dusseldorf (17)
- # clojure-greece (7)
- # clojure-italy (6)
- # clojure-russia (2)
- # clojure-spec (8)
- # clojure-uk (9)
- # clojurescript (93)
- # component (4)
- # copenhagen-clojurians (1)
- # cursive (24)
- # datomic (22)
- # editors (1)
- # emacs (8)
- # garden (2)
- # hoplon (357)
- # lein-figwheel (1)
- # leiningen (4)
- # luminus (27)
- # mount (13)
- # off-topic (7)
- # om (71)
- # onyx (35)
- # planck (3)
- # re-frame (53)
- # reagent (35)
- # ring-swagger (24)
- # specter (10)
- # sql (6)
- # untangled (47)
- # vim (157)
I am aot-compiling my source. Not doing any weird reloading anything.
I have seen NoClassDefFoundError in a worker thread during JVM shutdown. Normally I see it with Boot pods, where a timer is still active and it triggers between the time a needed class gets unloaded and the JVM shuts down. I would consider your -main
waiting on a promise that the shutdown hook delivers to be suspicious here.
I don’t know that I care that the promise is ever delivered, but I think that’s neither here nor there wrt the problem. The shutdown hook is barfing when it tries to call component/stop-system
I would add a println
inside your shutdown hook function — just to verify that it is not somehow being invoked twice (and it’s the second call that’s failing).