This subsection describes the procedure for dealing with problems that may occur during operation of an application server system.

Note that among the information to be acquired when a problem occurs, preparation before starting operation is required to acquire the information below.

• JavaVM log (JavaVM log file)
  The JavaVM garbage collection log is also output to this file.
  
• User dump (in Windows)
• core dump (in UNIX)
• OS statistical information (in Windows)

Perform preparations to acquire the information as and when required during system configuration. For details, see 3.2 Overview of data acquisition settings and 3.3 Execution environment settings.

To deal with problems that occur during system operation, follow the procedure in the figure below. The following figure shows the flow of the process for dealing with the occurred problem.

Figure 2-1 Flow for handling of data when a trouble occurs

1. Acquiring data
   Acquire all the required data for troubleshooting.
   For details about the data to be acquired, see 2.4 Types of Required Data. Note that a memory dump is required only when restarting a J2EE Server or CORBA Naming Service.
   Moreover, for details about methods of data acquisition, see 2.3 Acquiring the Data, or 4. Output Destinations and Output Methods of Data Required for Troubleshooting.
   

   Reference note

   • You can acquire the data either collectively as a snapshot log or acquire individual logs.
   • You can acquire snapshot logs using the management command and with the automatic acquisition as per the settings.
   • You can automate the process of acquiring required data when an error occurs in the logical server. For details, see 2.3.1 Data That Can Be Acquired Automatically When a Problem Occurs.

2. Identify the cause of the problem (Primary distinction)
   Identify the cause of the problem. Analyze the acquired data to identify the problem. For details about how to investigate data, see 5. Problem Analysis.
   
3. Troubleshooting and recovery
   Troubleshoot the cause of the problem and perform recovery.
   For details about dealing with each type of problem, see 2.5 Troubleshooting and Recovery.
   
4. Analyzing the cause of the problem (Secondary analysis)
   Analyze the cause of a trouble, as and when required. Request that maintenance personnel further analyze the cause of the problem.
   

   Hint

   For details on the troubleshooting specific to the time at which a problem occurs, see 6. Troubleshooting Procedure.