this might be a bit off topic, but if you want to profile your app in tomcat, Sun
Research has an experimental VM called JFluid. http://research.sun.com/projects/jfluid/
it is basically the jdk1.4.2_03 vm with hooks for profiling. it might help track down
GC and memory issues for those who don't have a license of OptimizeIt.
peter
Endre_St�lsvik <[EMAIL PROTECTED]> wrote:On Tue, 15 Jun 2004, Shapira, Yoav wrote:
|
| Hola,
Yo!
|
| >I know - but Sun's VMs surely seems to follow your suggestions!
|
| They might, and they might not, that's the point. Other VM
| implementations can choose to ignore System.gc(), or even Sun
| implementations on certain platforms (many J2ME installations ignore
| these calls).
Yes - and I suggested that one could try it out, just for kicks..! ;)
|
| That depends on your platform and settings.
Most definately - but Sun's VMs have been doing this for some time
(always?), and thus the gc() diff is interesting on this particular VM, at
least.
|
| >I have to debug this now, it will be interesting to see if it is Tomcat
| >code or my code that have the bug..! ;)
|
| It is expected that every reload will increase total memory usage,
| monotonically, it's not a bug, and there are numerous discussions about
| this and related issues in the arhicves.
Okay? Expected? I don't get that. Can you point me to a email-subject of
one of those threads? Or several?!
Thanks for info, anyway!
Endre.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
