Use of VisualGC (for memory leak detection mainly)
Execute the procedure below Action
Step.1 Install the tool on the machine where the JVM to debug is running (copy jvmstat directory using "rcp ?r etbf124:/osp/tmp/edel/jvmstat ." or transfer and extract jvmstat.tar from h:\users\in\edel\jvmstat. Install the tool in any directory: let?s call it <jvmstat directory>.
Step.2Start an X enabled session on the machine where the JVM to debug is running.
Step.3Get the process id of the JVM to debug: <JVM pid>
Step.4 Start the tool from <jvmstat directory>/bin using command "visualgc <JVM pid>"
Step.5 Follow up the memory consumption graphically ?. The "old gen" memory may vary but should not increase constantly when traffic is applied on the JVM.
Execute the procedure below Action
Step.1 Install the tool on the machine where the JVM to debug is running (copy jvmstat directory using "rcp ?r etbf124:/osp/tmp/edel/jvmstat ." or transfer and extract jvmstat.tar from h:\users\in\edel\jvmstat. Install the tool in any directory: let?s call it <jvmstat directory>.
Step.2Start an X enabled session on the machine where the JVM to debug is running.
Step.3Get the process id of the JVM to debug: <JVM pid>
Step.4 Start the tool from <jvmstat directory>/bin using command "visualgc <JVM pid>"
Step.5 Follow up the memory consumption graphically ?. The "old gen" memory may vary but should not increase constantly when traffic is applied on the JVM.
No comments:
Post a Comment