Arun wrote: > That worked finally with the increase in PermGen space. > I am a bit concerned about my server memory. > See my top (not mine ofcourse) > > top - 09:38:18 up 9:16, 3 users, load average: 0.27, 0.18, 0.10 > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 9770 root 25 0 491m 93m 35m R 102 4.6 0:13.64 java > > top - 09:38:33 up 9:16, 3 users, load average: 0.43, 0.22, 0.11 > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 9770 root 25 0 504m 138m 35m R 100 6.8 0:28.66 java > > top - 09:38:42 up 9:16, 3 users, load average: 0.52, 0.25, 0.12 > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 9770 root 25 0 512m 166m 31m R 100 8.2 0:37.63 java > > top - 09:39:03 up 9:17, 3 users, load average: 0.45, 0.25, 0.12 > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 9770 root 25 0 529m 175m 31m S 96 8.7 0:41.00 java > > top - 09:39:21 up 9:17, 3 users, load average: 0.42, 0.25, 0.13 > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 9770 root 25 0 561m 192m 31m S 9 9.5 0:47.93 java > > > See Mem: line and see the second one . It rises so fast . See at what rate.
Well, look at the CPU consumption at the same period - so your Tomcat is working on something. Looking at the amount of CPU time consumed, it could even be still running the application startup (Tomcat by itself can take something like 20 seconds of pure CPU time, on some machine architectures at least -- and here the CPU time usage is running from 13 to 48 seconds - so it's still too early to say whether the rise in memory usage will continue or not). > What is this PermGen space. Why does not it get garbage collected. PermGen is the holding space for the program code in your currently active classes. So, looks like whatever you're using has quite a large active codebase. > Is there anyway I can tell tomcat to suggest the VM a garbage collection > more often than the default garbage collection algorithm does. Is there any > declerative way of doing, xml, .sh? Even PermGen is cleaned in current JVM versions -- but classes can only be unloaded when there's no reference to the class within the JVM. And garbage collection overall is done when needed: it is definitely done before JVM throws an out of memory error. There's quite a lot of tunables for the JVM (including garbage collection), but pretty much you should trust the defaults (unless you have experience to actually distrust the defaults because of some specific feature in your application or runtime environment). -- ..Juha --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
