IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

---

Modify the garbage collection log path

The data collector configuration sets the path for the garbage collection log file...

• itcam_dc_gclog.log
• native_stderr.log

...to...

AppServer_home/profiles/profile_name/logs/server_instance_name

For example...

C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1

For version 1.3 JDKs, you cannot modify this. For other JDKs, to change the location or name of this log file:

1. In the file..
   DC_home/runtime/app_server_version.node_name.server_name/kwjdc.properties

   ...change the following parameter to point to the new garbage collection log file location:

   TEMAGCCollector.gclog.path=gc_logfile_path_and_name

   You can also optionally limit the size of the Garbage Collector logs.

   TEMAGCCollector.gclog.path=gc_logfile_path_and_name, x, y

   Where x and y are numbers. In this case, the logging will be performed to x files in rotation; information for y garbage collection cycles will be sent to one file before switching to the next file.

2. Log into the WAS administrative console for the instance of the application server for the data collector installed on the RMI server and click...
   Server \ Application Servers | server_name | Configuration tab | Server Infrastructure | Java and Process Management | Process Definition | Additional Properties: Java Virtual Machine

   ...and in the Generic JVM arguments field, change the following parameters to point to the new garbage collection log file location:

   JDK version	Parameter
   IBM 1.4 and 1.5	-verbosegc -Xverbosegclog:${SERVER_LOG_ROOT}/itcam_gc.log,5,3000
   Sun and HP 1.4 and 1.5	-Xloggc:gc_logfile_path_and_name -XX:+PrintGCTimeStamps

   Make sure the gc_logfile_path_and_name matches the value you specified in Step 1.

3. Click Apply.

4. In the Messages dialog box, click Save.

5. In the Save to Master Configuration dialog box:

   • If you are under a Network Deployment environment, be sure the check box Synchronize changes with Nodes is selected and then click Save.

   • If you are not under a Network Deployment environment, click Save.

6. Restart the instance of the application server monitored by the data collector.

Parent topic:

Customization and advanced configuration for the data collector

---

+

Search Tips   |   Advanced Search