|
> So when does the JVM actually start then? I am assuming > when the first call to a Java method is made because > that is where I see the performance hit > whilst in debug. I think that's right. So for an interactive job, you might: 1) Sign on 2) 0800 Run JavaMail - JVM starts 3) 0820 Run payroll all day - JVM still running 4) 1730 Run alphaWorks BattleBot - uses same JVM that started at 0800 And if you need a different CLASSPATH at 1730 than you did at 0800, you're stuck. It's time to sign off (end the JVM), sign on and start BattleBot (which starts a new JVM, picking up the new, different CLASSPATH). One way to avoid all these gyrations is to submit each Java program to batch, where it runs using it's own CLASSPATH. I am not nearly as sure what happens if you use QSHELL. Joe might have some insight there. --buck
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
