This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-05
Channels
- # announcements (11)
- # architecture (22)
- # babashka (33)
- # beginners (15)
- # biff (8)
- # calva (7)
- # clj-otel (1)
- # cljs-dev (3)
- # cljsrn (5)
- # clojure (76)
- # clojure-art (1)
- # clojure-europe (36)
- # clojure-hamburg (3)
- # clojure-nl (1)
- # clojure-norway (7)
- # clojure-poland (12)
- # clojure-spec (2)
- # clojure-uk (7)
- # clojurescript (9)
- # cursive (22)
- # data-science (6)
- # datomic (7)
- # fulcro (9)
- # hoplon (14)
- # instaparse (2)
- # jobs-discuss (14)
- # london-clojurians (1)
- # matrix (32)
- # music (1)
- # nbb (8)
- # off-topic (18)
- # pathom (29)
- # pedestal (6)
- # portal (34)
- # reagent (2)
- # reitit (4)
- # releases (1)
- # sci (10)
- # shadow-cljs (7)
- # tools-deps (4)
- # vim (6)
trying the new`add-libs` functionality, but because I have -Dcom.sun.management.jmxremote.port=17199 in JAVA_OPTS , when a new JVM is spawned it inherits that and tries to bind to that same port, so it throws an exception. Not sure how I can override this behavior, or if tools.deps should manage its own JAVA_OPTS
If you have that env var set globally, you can't start more than one JVM in general... How/where are you setting that?
It feels like something you should have under an alias, in :jvm-opts, so you can control when it's in effect. And then it won't interfere with other JVM instances.
I agree with Sean that that would be better (you can also pass on the CLI with -J-Dcom.... ), but this is something that we should at least you handle through a combination of https://clojure.atlassian.net/jira/software/c/projects/CLJ/issues/CLJ-2777 and https://clojure.atlassian.net/jira/software/c/projects/CLJ/issues/CLJ-2770 which are both things still in the queue