This discussion is archived
1 Reply Latest reply: Feb 28, 2011 8:55 AM by 699033 RSS

Question on Verbose GC output - JVM 1.5 on Solaris

843798 Newbie
Currently Being Moderated
Hi,

I noticed quite a few instances of the following lines in verbose gc file before the garbage collection. The output snippet is pasted below.

Application time: 4.1012270 seconds
Total time for which application threads were stopped: 0.0005752 seconds
Application time: 0.8841404 seconds
Total time for which application threads were stopped: 0.0032039 seconds
Application time: 0.4440765 seconds
Total time for which application threads were stopped: 0.0007130 seconds
Application time: 1.6186331 seconds
Total time for which application threads were stopped: 0.0008264 seconds
Application time: 0.4347317 seconds
Total time for which application threads were stopped: 0.0033167 seconds
Application time: 0.5889457 seconds
Total time for which application threads were stopped: 0.0009594 seconds
Application time: 1.6823893 seconds
Total time for which application threads were stopped: 0.0024016 seconds
Application time: 0.3524678 seconds
Total time for which application threads were stopped: 0.0463151 seconds
Application time: 0.4329528 seconds
Total time for which application threads were stopped: 0.0013379 seconds
Application time: 1.2358984 seconds
49.720: [GC 49.721: [ParNew: 306688K->0K(306944K), 0.1254446 secs] 306688K->16332K(1023744K), 0.1258293 secs]
Total time for which application threads were stopped: 0.1299930 seconds
Application time: 0.3679377 seconds


It is my understanding that this information is printed at the end of execution of any VM operation that requires stopping of all application threads (thread dumps, heap dumps, finding deadlock and GC). I do not find any heap dumps or thread dump on the server.

How can I find what is going on the server ? The fact it is occuring every second is what I am worried about.

The server is WebSphere 6.1 running on Solaris.JVM is 1.5.

Thank you for reading this post.

Vasu