IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Sustain large amounts of trace

If a large amount of calls is being traced, and some method data is not displayed in the Visualization Engine to configure the Managing Server to sustain large amounts of trace:

  1. Increase the method count limit of the Publish Server.

    The Publish Server maintains the method trace for the requests. There is a limit on the number of method entry or exits in this method trace. By default it is 10000. If any request has method records more than this count, the Publish Server truncates the method trace of a request in order to limit the total method entry or exit count to the configured value. By configuring the property Maximum Method Records you can control the number of method entry or exits in the method trace of a request. To increase the limit, change the property Maximum Method Records in the ITCAM for Application Diagnostics Managing Server. From the top navigation select Administration > Managing Server > System Properties. Change the value of Maximum Method Records to 50000 from 10000.

  2. Increase the Java heap size of the Archive Agent.

    The runtime memory of the Archive Agent needs to be increased as a potentially bigger method trace from the Publish Server. Set HEAP_MIN_SIZE_ARCHIVE_AGENT=1024 and HEAP_MAX_SIZE_ARCHIVE_AGENT=2048 in file MS_home/bin/setenv.sh to increase the Java heap size.

  3. Reduce the batch size of the Archive Agent.

    The Archive Agent will try to batch process a specified number of requests. The default is 20 requests. It will hit the limit of the IBM DB2 driver with the large requests. Change REQUESTDATA_BUFFER_THRESHOLD=20 to REQUESTDATA_BUFFER_THRESHOLD=1 in MS_home/etc/aa.properties.

  4. Increase the Java and JNI stack size of the Archive Agent.

    Even one big request might still hit the IBM DB2 driver limit. To avoid it, add -Xoss8M and -Xss8M in the Java startup command in the MS_home/bin/aactl.sh file. 

    ${JAVA_HOME}/bin/java -class path $CLASSPATH -Xoss8M -Xss8M

  5. Increase the query heap size of the IBM DB2 server to accommodate the large batch query from the Archive Agent as follows: 
    db2 update dbm cfg using parameter value
    For example, 
    db2 update dbm cfg using query_heap_sz 8000

Also, if the composite transaction tracking feature is enabled, increase the heap size of the GPS component. Set the following parameters in MS_home\bin\setenv.sh: 

HEAP_MIN_SIZE_SAM=256
HEAP_MAX_SIZE_SAM=1024


Parent topic:

Customization for the Managing Server on Windows

+

Search Tips   |   Advanced Search