Troubleshooting and support
This section provides information about how to troubleshoot a problem with your IBM® software.
Troubleshoot problems with your IBM software, using the problem determination tools provided with the product. For example, you can debug applications, add logging and tracing to your application, diagnose problems, use diagnosis tools, and troubleshoot WebSphere applications.
次主題
- How do I troubleshoot?
Follow these shortcuts to get started quickly with popular tasks. Debugging applications
To debug your application, you must use a development environment like the IBM® Rational® Application Developer for WebSphere to create a Java™ project. You must then import the program that you want to debug into the project.Adding logging and tracing to your application
You can add logging and tracing to applications to help analyze performance and diagnose problems in WebSphere Application Server.Configuring Java logging using the administrative console
Java logging provides a standard logging API for your applications. Before applications can log diagnostic information, you need to specify how you want the server to handle log output and what level of logging you require.使用高效能可延伸記載對應用程式進行疑難排解
您可以利用「高效能可延伸記載 (HPEL)」來協助診斷 WebSphere Application Server 中的問題。Using Cross Component Trace to troubleshoot applications
You can use Cross Component Trace (XCT) to help diagnose problems in WebSphere Application Server.Using sensitive log and trace guard
You can protect information with the sensitive log and trace guard. The sensitive log and trace guard prevents loggers from writing sensitive information in your log and trace files.Diagnosing problems (using diagnosis tools)
Various diagnosis tools are provided to help you determine the source and impact of problems occurring in your application serving environment.Using basic or traditional message logs to troubleshoot applications
WebSphere Application Server can write system messages to several general purpose logs, including JVM, process, and IBM service logs, which can be examined for problem determination.Working with trace
Use trace to obtain detailed information about running the WebSphere Application Server components, including application servers, clients, and other processes in the environment.Troubleshooting class loaders
Class loaders find and load class files. For a deployed application to run properly, the class loaders that affect the application and its modules must be configured so that the application can find the files and resources that it needs. Diagnosing problems with class loaders can be complicated and time-consuming. To diagnose and fix the problems more quickly, use the administrative console class loader viewer to examine class loaders and the classes loaded by each class loader.Choosing and using diagnosis tools and controls on z/OS
The following is a description of the types of tools and controls you can use for diagnosing and managing problems in the product environment.Using RMF
RMF™ can usually be started with the simple 'S RMF' command from the MVS™ console.Collecting job-related information with the System Management Facility (SMF)
SMF can be enabled to collect and record system and work-related information on the WebSphere for z/OS® system. This information can be used to bill users, report system reliability, analyze your configuration, schedule work, identify system resource usage, and perform other performance-related tasks that your organization may require.Choosing diagnostic information sources
You can use a variety of diagnostic information sources to view application data and troubleshoot problems.Configuring the hang detection policy
The hang detection option for WebSphere Application Server is turned on by default. You can configure a hang detection policy to accommodate your applications and environment so that potential hangs can be reported, providing earlier detection of failing servers. When a hung thread is detected, WebSphere Application Server notifies you so that you can troubleshoot the problem.Automation and recovery scenarios and guidelines
The following section provides information on how to monitor and recover WebSphere Application Server for z/OS and the subsystems it uses.Working with troubleshooting tools
WebSphere Application Server includes a number of troubleshooting tools that are designed to help you isolate the source of problems. Many of these tools are designed to generate information to be used by IBM Support, and their output might not be understandable by the customer.Working with Diagnostic Providers
Diagnostic Providers enable you to query the startup configuration, current configuration, and current state of a diagnostic domain. In addition, Diagnostic Providers can also provide access to any self diagnostic tests that are available from a diagnostic domain.Troubleshooting help from IBM
If you are not able to resolve a WebSphere Application Server problem by following the steps described in the troubleshooting topics, by looking up error messages in the message reference, or by looking for related documentation on the online help or the IBM support page, contact IBM Technical Support.Configuring the memory leak policy
The leak detection policy for the WebSphere® Application Server is turned off by default. You can configure a leak detection, prevention, and action policy to accommodate your applications and environment so that potential memory leaks are reported and acted upon. Leak detection, prevention, and proactive fixing provides for protection and resiliency for servers that face persistent out of memory errors. When a classloader memory leak is detected, WebSphere Application Server notifies you with informational messages in the log and by taking JVM heapdumps so that you can troubleshoot the problem. Optionally, you might also choose to have WebSphere Application Server mitigate, and if possible, fix the memory leak using reflection and other techniques.Collecting Java dumps and core files using the administrative console
You can use the Java runtime environment to create dump and core files to help with troubleshooting. You can use the administrative console to trigger the creation of these dumps and core files.目錄使用慣例
產品資訊中指向 app_server_root、profile_root 及其他目錄的參照,隱含特定的預設目錄位置。 請熟悉 WebSphere Application Server 中的使用慣例。Troubleshooting ActivitySessions
This page provides a starting point for finding information about ActivitySessions, a WebSphere extension for reducing the complexity of commitment rules and limitations that are associated with one-phase commit resources.Troubleshooting application profiling
This page provides a starting point for finding information about application profiling, a WebSphere extension for defining strategies to dynamically control concurrency, prefetch, and read-ahead.Troubleshooting batch applications
You can troubleshoot batch application issues using logging and tracing, or reviewing solutions to problems.對使用 Bean 驗證 API 的應用程式進行疑難排解
Bean 驗證 API 隨 Java Enterprise Edition 6 平台引入,用來作為標準機制,在應用程式的所有層(包括呈現層、商業層及資料存取層)中驗證 Enterprise JavaBeans。 在 Bean 驗證規格之前,會在每一層中驗證 JavaBeans。開發人員將驗證直接組合到它們的類別,或複製驗證程式碼(經常是雜亂的),以防止在每一層重新實作驗證。具有一個針對應用程式的所有層次所共用的實作,會簡化開發人員的工作,並節省時間。Troubleshooting client applications
This page provides a starting point for finding information about application clients and client applications. Application clients provide a framework on which application code runs, so that your client applications can access information on the application server.資料存取資源疑難排解
此頁面提供尋找資料存取相關資訊的起始點。各種企業資訊系統 (EIS) 利用不同的方法來儲存資料。這些後端資料儲存庫可能是關聯式資料庫、程序化交易程式或物件導向資料庫。疑難排解動態快取
這個頁面提供了一個起始點,可用來尋找動態快取服務的相關資訊,這項服務可快取 Servlet、指令、Web 服務和 JavaServer Pages (JSP) 檔的輸出,進而提昇效能。疑難排解 EJB 應用程式
此頁面提供尋找 Enterprise Bean 相關資訊的起始點。Troubleshooting messaging resources
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere Application Server.Troubleshooting naming and directory
This page provides a starting point for finding information about naming support. Naming includes both server-side and client-side components. The server-side component is a Common Object Request Broker Architecture (CORBA) naming service (CosNaming). The client-side component is a Java Naming and Directory Interface (JNDI) service provider. JNDI is a core component in the Java Platform, Enterprise Edition (Java EE) programming model.Troubleshooting Object Request Broker (ORB)
This page provides a starting point for finding information about the Object Request Broker (ORB). The product uses an ORB to manage communication between client applications and server applications as well as among product components. These Java Platform, Enterprise Edition (Java EE) standard services are relevant to the ORB: Remote Method Invocation/Internet Inter-ORB Protocol (RMI/IIOP) and Java Interface Definition Language (Java IDL).Troubleshooting OSGi applications
This page provides a starting point for finding out how to troubleshoot OSGi applications.Troubleshooting security
服務整合疑難排解
此頁面提供尋找服務整合相關資訊的起始點。Troubleshooting service mapping
This page provides a starting point for finding out how to troubleshoot service mapping.疑難排解階段作業起始通訊協定 (SIP) 應用程式
這個頁面提供了一個起始點,可用來尋找 SIP 應用程式的相關資訊,SIP 應用程式為使用至少一個已寫入 JSR 116 規格之「階段作業起始通訊協定 (SIP)」Servlet 的 Java 程式。交易疑難排解
此頁面提供了一個起始點,可用來尋找 Java 交易 API (JTA) 支援的相關資訊。在伺服器上執行的應用程式,可使用交易將資源的多個更新當作一個工作單位來進行協調,以便所有更新或沒有任何一個更新會成為永久的。Web 應用程式疑難排解
此頁面提供了一個起始點,可尋找 Web 應用程式的相關資訊;這些 Web 應用程式是由可以當作一個單元來管理的一或多個相關檔案組成,其中包括:Web 服務疑難排解
此頁面提供尋找 Web 服務相關資訊的起始點。


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=welc6toptroubleshooting
檔名:welc6toptroubleshooting.html