×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
A framework like what Dieter has done stays running as a background app and calls are made to it at runtime, so no new instances of Java being spun up for each call.
RUNJVA or JAVA call and create anew JVM for each call.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Wed, 22 Sep 2021 11:02:41 +0200
from: john erps <jacobus.erps@xxxxxxxxx>
subject: Java execution on IBM i
Hi,
I have a question regarding the execution of java programs on IBM i.
I'm a bit confused.
I always thought that it was a good idea to execute java programs/functions within one server job. The requesting job sends a message to the server job, and the server job executes it. This way, the JVM is initialized only once. I believe Dieter even has a framework to do this.
However, as i understand it. If i use command JAVA or RUNJVA to execute a java app it is executed within a separate BCI job. I suppose (maybe i'm
wrong) this BCI job keeps running after the command has been executed. Next time the command is executed the same (or another already initialized) job executes the java function.
My confusion is why is it a good idea to implement a dedicated Java server job yourself, like Dieters framework, as this seems to be already working like that when using RUNJVA?
What am i missing?
midrange.com
