WebSphere监控工具使用情况大调查！

Nmon还是很不错的 收起

用过nmon，不过主要是监控操作系统的信息吧 收起

现在的监控工具很火啊 收起

这个也是好东西

MustGather: Performance, hang, or high CPU issues on AIX
Technote (troubleshooting)

Problem(Abstract)
If you are experiencing performance degradation, hang, no response, hung threads, CPU starvation, high CPU utilization, network delays, or deadlocks, this MustGather will assist you in collecting the critical data that is needed to troubleshoot your issue.
Resolving the problem
If you are experiencing performance degradation, hang, no response, hung threads, CPU starvation, high CPU utilization, network delays, or deadlocks, this MustGather will assist you in collecting the critical data that is needed to troubleshoot your issue.
To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.

Collecting data manually
Complete the following 3 steps.
1.        Collecting required data:
If you have not already done so, enable verboseGC and restart the server.

At the time of the problem, run one of the attached scripts with the appropriate command:

For WebSphere Application Server 6.1 and later:
./aixperf.sh [PID]


For WebSphere Application Server 6.0 and earlier:

./aixperf60.sh [PID]

Note: Both aixperf60.sh and dbxtrace_aix.sh should be in the same directory and dbx must be installed to diagnose high CPU issues.
  

In the above commands [PID] is the Process ID of the problematic JVM. This step will create a file named aixperf_RESULTS.tar.gz as well as 3 javacores. These scripts must be run as the root user.

2.        Collecting log files:
Collect the server logs from the problematic server:
profile_root/logs/server_name/*

3.        Submitting required data:
Zip or Tar all the output and log files:
•        aixperf_RESULTS.tar.gz
•        3 javacores
•        Server logs

Send the results to IBM Support.


Frequently Asked Questions:
•        What is the impact of enabling verboseGC?
VerboseGC data is critical to diagnosing these issues. This can be enabled on production systems because it has a negligible impact on performance (< 2%).
•        What is the aixperf_RESULTS.tar.gz file and where can I find it?
The aixperf_RESULTS.tar.gz file is created while running the aixperf.sh script and contains output from the commands called by the script. It will be created in the directory from which you execute the script.
•        What are 'javacores' and where do I find them?
Javacores are snapshots of the JVM activity and are essential to troubleshooting these issues. These files will usually be found in the profile_root. If you do not find the files here, you can search your entire system for them using the following command:
find / -name "*javacore*"

•        Is there another way to gather the required data?
Yes. If you prefer to run the commands manually, run these commands while the issue is occurring:
ps avwwwg > ps.out
kill -3 [PID]
vmstat 5 12 > vmstat.out

Note: This command will take one minute to complete.

tprof -skex sleep 60

Note: This command will take one minute to complete and will generate a file named sleep.prof.

kill -3 [PID]
./dbxtrace_aix.sh -a [PID] > dbxtrace.out


wait two minutes

kill -3 [PID]

Note: You only need to run the dbxtrace_aix.sh script if you are diagnosing a high CPU issue on WebSphere Application Server 6.0 or earlier.

•        What if I am using WebSphere Application Server 5.1? Where are the server logs?
For WebSphere Application Server 5.1 the server logs will be here:
install_root/logs/server_name/*


If asked to do so:
The preceding data is used to troubleshoot most of these issues; however, in certain situations Support might need additional data. Only collect the following data if asked to do so by IBM Support.
•        System core
You can collect a system core by executing the following command:
gencore [PID] core.[PID]

Process the system core file using the instructions in MustGather: Crash on AIX.


•        Monitor process sizes and paging usage
The aixmon.sh script will collect data every 5 minutes until it is stopped manually. Run the following command before the issue occurs to start the script:
./aixmon.sh

This will create two files: ps_mon.out and vmstat_mon.out.




Related information
How to enable verbosegc in WebSphere
IBM Thread and Monitor Dump Analyzer
Submitting information to IBM support
Steps for getting support for WebSphere Application Server
MustGather: Readme first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server
Checking if the dbx utility is installed on AIX

Exchanging data with IBM Support
To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:
•        IBM Support Assistant (ISA)
•        Service Request (SR)
•        E-mail
•        FTP to the Enhanced Customer Data Repository (ECuRep)
Read first and related MustGathers
MustGather: Read first for WebSphere Application Server
________________________________________
Crash problem Out of Memory Problem

Cross Reference information
Segment        Product        Component        Platform        Version        Edition
Application Servers        WebSphere Application Server - Express        Hangs/performance degradation        AIX        7.0, 6.1, 6.0.2, 6.0.1, 6.0, 5.1        
Application Servers        Runtimes for Java Technology        Java SDK 收起