Fork me on GitHub
#boot
<
2019-12-05
>
dazld16:12:27

hi everyone, i’m debugging an issue where a colleague’s BOOT_JVM_OPTIONS env var is being ignored

dazld16:12:41

did any of you come across something like this?

dazld16:12:52

we can see it in (System/getenv)

dazld16:12:58

but… seems to be ignored

alandipert17:12:06

@dazld hm, how are you running System/getenv?

alandipert17:12:28

also, what system/bash version is your colleague on?

Claudiu-Vlad Ursache17:12:42

@alandipert @dazld's colleague here the bash version I'm running:

api (benchmark) $ bash -version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)
Copyright (C) 2007 Free Software Foundation, Inc.
we simply tried out boot repl and ran (System/getenv) inside. the BOOT_JVM_OPTIONS is set to the correct values, but the datomic valcache flags are not propagated

dazld17:12:04

we’re looking at (System/getProperties) too

dazld17:12:20

the jvm flags are just ignored

alandipert17:12:30

and the BOOT_JVM_OPTIONS variable is set to the same thing on both your machines… but it just doesn’t work on @claudiu511’s machine?

dazld18:12:07

That’s exactly it

dazld18:12:19

It’s super weird

dazld18:12:14

Set the properties directly and everything works, but for whatever reason, the Java process that boot starts didn’t see them

dazld18:12:18

There’s something fishy about how boot is starting java on claudiu’s machine

dazld18:12:02

It sees the environment var but those options aren’t set

dazld18:12:52

He’s using sdkman if that’s relevant

flyboarder18:12:06

What version of boot on each machine?