标签：Trace trace up WebSphere Maximum Server Application

Setting up a trace in WebSphere Application Server

Troubleshooting

https://www.ibm.com/support/pages/setting-trace-websphere-application-server

Problem

Use this document to set up trace strings for IBM WebSphere Application Server as mentioned in the component-specific MustGather documents.

Resolving The Problem

Note, the trace string you use depends on what module or component in WebSphere Application Server you need to trace, or what problem you are wishing to troubleshoot. Trace file Maximum file size and the Maximum number of historical files suggested is sufficient for most cases. For large environment set Maximum number of historical files to 30(captures 3gb trace approx).

To determine which trace string you need, go to MustGather: Read first for WebSphere Application Server for a listing of product components that matches your symptom.

For WebSphere Application Server V8.5 Liberty profile, use Setting up trace and getting a full dump in the WebSphere Application Server V8.5 Liberty profile


Static trace:

1. Log on to the administrative console.
    
2. In left panel expand Troubleshooting. Click on Logs and Trace.
    
3. Select the application server to be traced, and then on the next page click the Diagnostic Trace link.
    
4. Select the Configuration tab.
    
5. Under Trace Output, select File radio button and specify File Name. Also Increase the Maximum file size to 100 MB and Increase the Maximum number of historical files to 10.
    
6. Select Basic (Compatible) Trace Output Format unless otherwise specified by support.
    
7. On same panel click on Change Log Detail Levels under Additional Properties on right side panel.
    
8. Under Configuration tab specify Trace Specification by entering the trace string specific to the MustGather documentation for which you are collecting data.
    
9. Click Apply and OK. Then Save your configuration (select Synchronize changes with Nodes option)
    
10. Restart the server to begin tracing.

Dynamic trace:

1. Log on to the administrative console.
    
2. In the left panel, expand Troubleshooting and click on Logs and Trace.
    
3. Select the application server to be traced, and then on the next page click the Diagnostic Trace link.
    
4. Select the Runtime tab (Server should be up and running for this tab to show up).
    
5. Under Trace Output, select File and type a File name (if you do not specify path, but just the file name, then the default location of the file is under the application server profile directory). Set the Maximum File size to 100Mb and Maximum Number of historical files to 10.
   
   Important: Do not select Save Runtime Changes to Configuration as well if you do not want this setting to become permanent.
    
6. On same panel click on Change Log Detail Levels under Additional Properties on right side panel.
    
7. Select the Runtime tab.
    
8. Under Trace Specification, enter trace string for the specific MustGather for which you are collecting data.
    
9. Click Apply and OK. Then Save your configuration (select Synchronize changes with Nodes option).
    
10. Server does not require a restart.

Stopping trace:

1. Remove the trace string from Trace Specification in the appropriate trace tab(s) (Configuration and/or Runtime).
    
2. Click Apply and OK. Then Save your configuration (select Synchronize changes with Nodes option).

   

标签：Trace,trace,up,WebSphere,Maximum,Server,Application
来源： https://www.cnblogs.com/z-cm/p/16525033.html

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。