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!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.