|
I have noticed that once a jar is loaded into memory (when a class file in the jar is called), it stays in memory even if I replace the jar with a newer version or even delete the existing jar. For example:
1. Place new .jar file on the iSeries 2. Run a program that uses a class inside the .jar file 3. Delete the .jar file4. Run the same program again, and is still runs because the Java class it uses is still in memory somewhere.
How does class loading work on the iSeries? How do I reset things so that I can replace a .jar file with a newer version and have the updated classes loaded and run instead of the cached classes?
The only work around I have found is:1. Start a new session. 2. Delete the jar. 3. Call the class file, and get the ClassNotFoundException
4. Copy over the new jar. 5. Sign off/back on again.6. Call the class file again (now see message "Attaching Java Program to ..."). The new class file/jar is now used.
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.
midrange.com
