|
Guys, I think the main reason why there aren't system wide JVMs is for code security/stability. Wouldn't it be kinda crazy if all Java processes were using the same JVM? Processes could just start screwing with other processes session type objects whenever they felt like it. What about garbage collection in this huge JVM? As far as I know the iSeries is a bit different in terms of GC compared to the typical background process. The iSeries JVM actually pauses execution in the JVM to do clean up. I think we would have alot of clean-up to do if we have processes entering and leaves the same JVM all the time. Just throwing out what I see as some potential problems... Regards, Jim. ********************************************************************** This electronic message contains information from Russell A. Farrow Limited, Russell A. Farrow (U.S.) Inc., Canadaplus.com or RAFXpress that may be confidential or privileged. The information in this electronic message is only for the use of the intended recipient. Inappropriate disclosure, copying, distribution or other use of the contents of this electronic message is strictly prohibited. If you have received this electronic transmission in error, please notify the sender immediately by return e-mail. Thank you. ***********************************************************************
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.