timob
commented
3 years ago You need to call AttachCurrentThread on the *JVM. This returns a new *Env which can used in the current thread. And then call DetachCurrentThread when your done.
One way to do this so you don't have keep attaching threads is something like:
var funcChan = make(chan func(*jnigi.Env))
func RunOnJavaAttachedThread(f func(*jnigi.Env)) {
funcChan <- f
}
// run with go keyword from main
func RunJavaThreadFuncs(jvm *jnigi.JVM) {
env := jvm.AttachCurrentThread()
for f := range funcChan {
f(env)
}
}
/*
In end-point handler
RunOnJavaAttachedThread(func(env *jnigi.Env) {
// run my java code here
})
*/This means that bits of Java code will be only run one at a time. You could use sync.Pool if you want to handle more than one at a time.
One thing to note is AttachCurrentThread calls runtime.LockOSThread. I might change this in the future so that the program it self calls this.
yissatayev
Hi,
If I initialize JVM (load, create, etc.) in the main function, I can successfully execute a Java code without any problems. However, If I try to initialize JVM only once after the application has started instead of initializing for each call and call a Java code in handler functions, I get the following error:
Could you please help with what I am trying to achieve? Basically, I want to create an end-point in a Go application which will call some Java code each time request is received.
The sample code I am working with is here TinkJNIGo