Sun Microsystems Portal Server 6 2005Q1, Planning Manual

Page: 165 / 192

Troubleshooting SRA
Appendix D Troubleshooting Your Portal Deployment 165
At the end of the test period, run
shooter
to collect the output of
gctool
along with
other data.
memfoot.sh
This script tracks the memory footprint of a process. Start this script after starting
the Gateway and allow it to run during the duration of the test. The largest process
with the given name or PID is tracked after every specified number of seconds.
To run
memfoot
, type:
./memfoot java 60
The output of this script is a time-stamped process status file. The
shooter
tool
collects this output along with the rest of the data.
uniq.pl
This script is used internally by
shooter
to find unique lines and their count. The
advantage over the system
uniq
script is that it finds non-adjacent unique lines.
GWDump.class
This class is called internally by
shooter
to obtain the Gateway settings in the
Access Manager administration console.
SRA Log Files
Examine the following log files for errors.
Gateway:
/var/opt/SUNWps/debug/srapGateway_
Gateway-hostname
_
Gateway-profile-name
NetFile:
NOTE
Before running
gctool
, ensure that you include
-verbose:gc
in the
Gateway script in the “CMD” section. The Gateway script resembles
the following:
-server -verbose:gc -Xms1G -Xmx2G
-XX:+OverrideDefaultLibthread -XX:ThreadStackSize=128
-XX:MaxPermSize=128M -XX:PermSize=128M -XX:MaxNewSize=256M
-XX:NewSize=256M