opened 07:31PM - 18 Feb 19 UTC
closed 03:59PM - 25 Feb 22 UTC
regression
In 1.1, trying to initialise the java virtual machine in Julia via JavaCall.jl c… auses a stack overflow error. It works correctly when the code is loaded with `-i` or `-e` but fails when used from the REPL.
```
ERROR: StackOverflowError:
Stacktrace:
[1] init(::Array{String,1}) at /Users/rene/.julia/packages/JavaCall/toamy/src/jvm.jl:176
[2] top-level scope at none:0
```
Ref: https://github.com/JuliaInterop/JavaCall.jl/issues/96
The call in question is the `JNI_CreateJavaVM` function in the JVM. More information about the JVM invocation API is at https://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/invocation.html
This is a regression from 1.0.x
Julia 2.0 is mentioned nowhere. Also being discussed over here:
I saw in a thread: “we have effectively lost the JDBC wrapper until Julia 2.0”.
This isn’t strictly true, as it still works in Julia 1.0.x, the LTS versions for the foreseeable future.
But, yes, Julia 1.1, if I recall, broke JavaCall.jl and thus JDBC and I guess Scala/Spark too. [And for JDBC there are workarounds.]
I’ve promoted Julia’s “syntax stability guarantee”, since Julia 0.7. I do occationally see packages being fixed for 1.1, 1.2 or 1.3. I realize there can be changes in the standard…
The only place that I can see anyone talk about “we have effectively lost the JDBC wrapper until Julia 2.0” is your post that said that. Where are you getting this idea from?