On 2/7/2014 12:56 PM, Jon Paris wrote:
The basic reason this occurs is because the JVM grabs the
environment variables when it starts - and since it can only be
started _once_ per job, all required jars need to be available when
it first starts. The "cure" of sign off and back on again works
because the JVM will be restarted in the new job.

Alternatively, if the java program doesn't effect the interactive job, you can make the java app a server job and create a native program (RPG, Cobol, or CL) can send requests to.

This way you only have a single instance of the java app running.

Data queues are my choice for communicating between java & native apps.

david




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.