@alandipert: @micha Howdy? I'm trying to start the new socket server that ships with Clojure 1.8 with BOOT_JVM_OPTIONS. It doesn't seem to work. I think it's because shimdandy (address already in use). Thinking about a solution, I was wondering if it is possible to launch a pod with separate JVM options?

Maybe I'm doing it wrong, but the official examples talk about starting the JVM with a system property like -Dclojure.server.repl="{:port 5555 :accept clojure.core.server/repl}" that the Clojure runtime will pick up at boot time.

@danielsz: do you get an actual error?

@martinklepsch: Boot exits with an error (sometimes silently).

Boot starts multiple Clojure runtimes via shimdandy, so I'm not surprised it doesn't work.

@danielsz: how do you setup/start Boot?

@martinklepsch: Normally. Are you asking because you've had different results?

yeah, I set the JVM options and started a repl/called clojure.main/main but I think I'm doing something wrong

@martinklepsch: I typed export BOOT_JVM_OPTIONS="-Dclojure.server.repl='{:port 5559 :accept clojure.core.server/repl}'" in the shell. Then I ran boot.

running boot with boot repl?

Not necessarily. Even boot -h won't work.

now I see it, thanks

tried different JVM options before

I speculate it has to do with shimdandy and multiple Clojure runtimes.

However, the problem of starting the socket server can be solved easily, by using the API. So no big deal.

yeah makes perfect sense, was just confused because I couldn't replicate

Users will likely try the system property approach first, because that's what the docs talk about. And that will be a problem with Boot. We need to tell them to use the API (http://clojure.github.io/clojure/clojure.core-api.html#clojure.core.server/repl) @alandipert @micha might come up with something.

definitely, should be added to docs or so

Yeah, I'll write something in the wiki.

@danielsz: add if there's something missing ^

@danielsz: nice!