Garbage collection is a common cause of performance issues which cannot be detected from the TeamConnect Performance Monitor logs. Garbage collection logging should be on in production environments and these logs should be analyzed in conjunction with the TeamConnect Performance Monitor logs. Mitratech typically recommends these GC logging settings for the Sun JVM:

-XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:-TraceClassUnloading

Optionally include -Xloggc:<file> if the application server is not capturing stdout to a log file. The only downside to this option is that it overwrites <file> on every restart, which can erase valuable information.

Use this GC logging setting for the IBM JVM:

-verbose:gc

This setting is the same as enabling the Verbose garbage collection checkbox in WebSphere administration console.