12.2.3 If a poor response was reported
If a poor response was reported from an administrator of a business application program, or if application program processing timed out due to a poor response, acquire error information to investigate the cause on the EADS servers and EADS clients.
- Organization of this subsection
(1) Error information to acquire on the EADS servers
Acquire the following information on all EADS servers:
-
Statistics
-
Thread dumps
-
All files under the directory specified in the eads.logger.dir parameter in the server properties
-
All property files under management-directory/conf
For details about how to acquire error information, see 12.3 Acquiring error information.
(2) Error information to acquire on the EADS clients
Acquire the following information on all EADS clients:
-
All files under the directory specified in the eads.client.logger.dir parameter in the client properties
-
Client property file
(3) Items to check with the administrator of business applications
Check the following with the administrator of the business application program:
-
Is there any regularity in the time period in which the response has become poor?
-
Has a poor response occurred repeatedly on the same EADS client?
-
Is there any regularity in the sorts of operations that result in a poor response?