Had the same problem here that the JVM is starting with every time I call
the command (its not really a problem because that is what is supposed to
happen: you call the program, the JVM starts, executes your program and
once its done, quits the VM again).
My “fix” for this problem was to change my program to start up once and
then scan a folder for a txt file that contains all the parameters that
would usually be handed over to the program. Once it detects a text file,
it opens a new thread to process it and once done, the thread is closed but
the program itself keeps running. This way it can also handle multiple
requests in parallel. The text file is created by the CL that would have
usually called my program before the fix.
I assume the correct solution would be to set something up like an
application server that runs your application and is then called by the CL
but no clue if that is
a) the correct approach and
b) how to do that ;)
Hope that helps!
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.