|
Richard Shaler wrote: > ... > Assuming I'm not going to call any more Java methods in the current job, > would destroying the JVM still be a viable alternative to explicitly cleaning > up objects? > No. In V5R1, if you destroy the JVM, you may not be able to start a new one the way you want (for example, if you need to call JDK 1.2+ methods). In V5R2, you can't start a new one. I don't completely understand this, but even in V5R1, destroying the JVM doesn't really destroy it, it just makes it unusable. Some threads are still allowed to continue running. Anyway, the upshot is - don't build a dependency on being able to destroy the JVM.
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.