|
On May 6, 2024, at 1:15 PM, Ali Ekinci via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Using JNI methods to create JVM. I am aware of the limitation (at least it was the case) that a single IBMi job allows only one JVM and restart is not possible when it ends.
A third-party application is making java calls and requires java classpath to be changed. Once internal processes starts JVM, then third-part application fails. Or vice versa when the third-part app is executed first.
Obviously, a workaround is to submit the third-party action to a batch job.
I thought that potentially IBM eased the "one JVM per job" restriction by allowing different JVMs in each activation group.
Is there any change in that area?
Thanks for any help in advance.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.